@Rmano Sorry, no more bacon for you: oddstuffmagazine.com/funny-pictures-september-25-2021.html/…

@samcarter Oh, no! (well, I prefer "guanciale" anyway)

@samcarter ooh

ooh a plot

@PauloCereda "1959 threw 2001" is an interesting statement

@Rmano had to look that one up, but the wikipedia entry makes it sound very tasty! :)

@PauloCereda :D I'm not sure what is worse: the content of their message or the bad job they did with the typography :)

@Rmano :)

@samcarter LOL

... I wonder why my cat used to catch birds? Did she need the parts for some electronics projects?

@PauloCereda Hitchcock knew that already ...

@UlrikeFischer ooh

@DavidCarlisle miktex removed the type1 directory from fontconfig: github.com/MiKTeX/miktex/issues/940

@UlrikeFischer maybe I should ask again at texlive:-)

@DavidCarlisle you mentioned that it is so in miktex ;-)

@CarLaTeX sorry I wanted to comment on your crash question but then got distracted. Imho reinstalling in such cases is the best. It costs much less time than trying to figure out what is still working and what is damaged.

@PauloCereda I'll be praying for that guy.

@yo' <3

@UlrikeFischer Don't worry. Prof. van Duck and I are in Florence now

@CarLaTeX ^^^ they have plans ...

@UlrikeFischer Lot's of holes in the ground there -- perfect for meerkats :)

When invoking a function as in __mandi_newscalarquantity:nnnn { #1 }{ #2 }{ #3 }{ #4 } should I remove the white space around the arguments?

(the backslash before the double underscore didn't show up for some reason)

@LaTeXereXeTaL use backticks to show \command

`\likethis

@LaTeXereXeTaL if you are in the scope of expl3 syntax (which you presumably are) all white space is ignored

@LaTeXereXeTaL no one at each end (same as inline code on the main site)

\likethis

Ah okay.

@DavidCarlisle I know, but the expl3 docs state braced isolated arguments shouldn't contain white space. I'm just looking for the bottom line (if there is one).

@LaTeXereXeTaL which doc section, I'll look what it says, but the white space is ignored so it isn't refering to this use.

@DavidCarlisle Page 13 of the current expl3.pdf. I'm unsure whether the situation I showed comes under that or not.

@DavidCarlisle I'm going through lots of code today and I want to standardize the style and I want to get it right.

@LaTeXereXeTaL ah that's just a code formatting suggestion, it makes no actual difference.

@DavidCarlisle Okay thank you. My biggest fear of using this site is being consistent with recommendations amongst all the knowledgeable people. I want to make everyone happy.

@LaTeXereXeTaL I stick to \zzzzz and people seem happy enough. doesn't quite match the "Use long, descriptive names for functions and variables" rule on that page though

@DavidCarlisle Well I already told you it makes me happy.

I blame @UlrikeFischer tex.stackexchange.com/a/618256/1090

@DavidCarlisle it is a bit surprising, I would have expected the tilde to have catcode 12. Does it have a special meaning in lua?

@UlrikeFischer no I think it's just failing to handle active characters correctly. secret plan is to get @MarcelKrüger interested to look at it,

@DavidCarlisle hm, the definition of ~ begins with \n

@DavidCarlisle If I do \def~{\penalty500{}} then I get the error (with directlua) invalid escape sequence near ''First\p'

@UlrikeFischer not releated to ~ you get same with an active L

\catcode`L=13

\initcatcodetable10
\savecatcodetable10

\def L{zzz}

   \directlua{
        token.set_macro(0,'NAME','First \stringLast','global')
}

\immediate\write200{\meaning\NAME}


\def\zz#1{\immediate\write200{\meaning#1}\ifx!#1\else\expandafter\zz\fi}

\expandafter\zz\NAME!

   \directlua{
        token.set_macro(10,'NAME','First \stringLast','global')
}

\immediate\write200{\meaning\NAME}


\def\zz#1{\immediate\write200{\meaning#1}\ifx!#1\else\expandafter\zz\fi}

\expandafter\zz\NAME!

@DavidCarlisle the comment of Henri here tex.stackexchange.com/questions/519954 is interesting ...

@UlrikeFischer hmm excellent answer there but....

@DavidCarlisle yes not very conclusive.

One gets many points from a simple ghost ...

@UlrikeFischer Andrew's posted a proper hobby answer though

@DavidCarlisle yes, and the animated one is nice too.

@UlrikeFischer Great!

@DavidCarlisle Catcode 13 is not handled like other catcodes in LuaTeX and instead inserts a special kind of control sequence. This special case isn't implemented in set_macro and therefore you get the token which would represent a character token with catcode 13 if such a thing would exists. The first command defined in TeX is \par (and therefore has command code 13), so it effectively behaves like \par (but is different in a \ifx sense)

@MarcelKrüger yes I figured it was something along those lines but hadn't got to the fact that it was actually \par would have an interesting effect on the par hooks, makes the discussion about \endgraf seem easy:-( so basically the answer is, it doesn't work?