@JosephWright, @DavidCarlisle since you didn't do it, I finally added the new kernel key=val system to the big list: tex.stackexchange.com/a/648785/117050
@JosephWright Allowing package writers to define new properties would open several compatibility problems: suppose packages A and B both define .mycode:n…
@JosephWright if he wants to programmatically add some macro in the front of all of his keys in a single \keys_define:nn call, I'd suggest to use some preprocessing step using \keyval_parse:NNn: \cs_new:Npn \ljr_preproc:nn #1#2 { , \exp_not:n { #1 = { \ljr_functional_stuff_whatever: #2 } } } \cs_new:Npn \ljr_preproc:n #1 { , \exp_not:n {#1} } \keys_define:nx { ljr } { \keyval_parse:NNn \ljr_preproc:n \ljr_preproc:nn { <real-list-of-definitions> } }.
@daleif been so long since I was on a concert... On Sunday I'll see Die Ärzte.
@Skillmon as you can see on the image there was waaaayyyy to many people there. It took us 40min to get out of our small stadium due to several bottlenecks.
Regarding the new key-val interface in the 2022 format, are there global-scope counterparts for .store and .if? Or can I use .bool_gset:N in my l2e package?
@Skillmon you'd need to go back pre l3build, but arguably it's like example-input.png and a file available for tests, that is one reading of the doc in verbatim.dtx