[01:04:14] <taylan>	 Would it be theoretically possible for an extension to modify the parser such that {$foo} actually works as a synonym to {{{foo}}} in template definitions?
[01:07:55] <bawolff>	 taylan: Extensions can replace the MW parser with a different parser (e.g. you can make an extension to replace wikitext with markdown, etc)
[01:08:13] <bawolff>	 So in theory you can write your own parser that is exactly like the normal one but with different variable syntax
[01:09:04] <taylan>	 well, that would be copy-paste programming :P
[01:09:32] <bawolff>	 alternatively i guess you could use a hook like onParserBeforeInternalParse to replace the syntax. I wouldn't really reccomend modifying the parser on such a deep level though
[01:10:13] <taylan>	 since there's some extensions that add <foo> and {{#foo}} kind of stuff I thought maybe {$foo} could be done, but I guess the really "modular" way to do it is constrained to <> and {{#...}} ?
[01:10:17] <bawolff>	 i imagine doing such a thing would also break VE
[01:10:52] <bawolff>	 <foo> and {{#bar are intentional extension points though, that are kind of built in
[01:11:00] <taylan>	 thought so
[01:11:26] <taylan>	 what are the odds MW would accept a patch that adds {$foo} as a built-in synonym to {{{foo}}} ? :D
[01:11:59] <taylan>	 anyway I don't really have time to work on it even if it were to be accepted
[01:12:27] <bawolff>	 basically 0 :)
[01:13:09] <bawolff>	 At this point we're extremely reluctant to accept new wikitext features unless it solves a major problem
[01:13:22] <bawolff>	 Wikitext is already quite complex, so we don't really want to add to it
[01:22:29] <Archimedes1560[m>	 <taylan> "what are the odds MW would..." <- How is this better
[01:22:29] <Archimedes1560[m>	 Less characters?
[01:22:56] <taylan>	 yeah, nested {{{foo|{{{bar}}}}}} is kind of ridiculous
[01:23:10] <taylan>	 {$foo|{$bar}} this would be such a breath of fresh air
[01:25:59] <Archimedes1560[m>	 I think closing brackets merging is more of an issue
[01:26:45] <Archimedes1560[m>	 So something like {foo$} would make more sense
[01:27:13] <Prod[m]>	 what happens if you want to use { or } in text?
[01:29:01] <Archimedes1560[m>	 Nothing, unless you also used the dollar sign
[01:43:27] <lehran06050[m]>	 Not a compelling enough use case to merit adding new wiki markup syntax because the old way should still need to remain supported indefinitely
[01:45:32] <Archimedes1560[m>	 Make it a config value with special page for converting
[02:09:33] <taylan>	 does the 1.39 version of CirrusSearch work with ElasticSearch 8.x?
[03:21:32] <taylan>	 I've since learned it doesn't, installed ES 7
[03:22:42] <taylan>	 I have a weird problem with Cirrus... background info: I use "t" as a namespace alias for "Template"...
[03:23:13] <taylan>	 When I enter t:mai into the search field, I get the autocomplete suggestions for T:MainPageDesktop and T:MainPageMobile, but as soon as I continue typing and it becomes t:main, those suggestions disappear
[03:23:48] <taylan>	 they don't appear for t:mainp either, but with t:mainpa they appear again
[03:24:07] <taylan>	 hmm, I guess this is related to the "intelligent" algorithm of ElasticSearch somehow
[03:30:41] <taylan>	 huh it works now, something must have been updated in the background