https://tug.org/members/TUGboat/tb44-2/tb137egger-edith.pdf (on the page @samcarter provided there was a link)
(If someone would like something entertaining to read, I can recommend "New dimensions: Edith and Tove")
The TUG23 proceedings are now available: https://tug.org/TUGboat/Contents/contents44-2.html
A package with `robust` in the name is like an invitation to break it :)
Good package. Now all we have to wait for is a more thorough and better integrated `l3fp` into Ti*k*Z so `pgfmath-xfp` becomes obsolete.
AFAIK, the problem is that the `xspace` macro that (basically) checks if a letter or punctuation comes next, may be followed by tokens (from user or package code) that are not category 11 or category 12 tokens, rather expandable tokens that, after some expansion and possibly execution steps that `xspace` has no way to know (think non-expandable loops), may append items to the horizontal list, items which may ultimately appear as horizontal space, letters or punctuation. In short, `xspace` can't see through the future execution of TeX code that follows its main macro.
It is not always easy to see what comes after something. Good crystal balls are hard to get.
Why is it so difficult to predict the places where an approach like `xspace` _may_ fail? I am never gonna use that package tbh, because I personally don't find adding `\` or `{}` that serious a problem, but I am curious to know why it is so difficult to predict the consequences of `xspace`.
David Carlisle [wrote](https://tex.stackexchange.com/a/86620/73317): > I originally implemented `xspace` a long time ago (for LaTeX 2.09) (...). > > The rule in TeX is really quite simple, after a command name that uses letters (as opposed to single character command names using non-letters such as `\$`) white space is ignored. It is easy to forget to use `\` or `{}` but the result of forgetting is very predictable, you lose white space in the result. Conversely with `xspace` the macro will get the correct space most of the time, but it isn't easy to predict when it will get it wrong, and so it's much harder to learn to enter the markup in a way that is always correct rather than having to always visually check for missing space, which rather negates the purpose of the command. > > So, if you find it useful, fine, it's there. But personally I wouldn't recommend it.
I'm sure I remember him advocating against its usage, but knowing David, most likely yours is the more probable take.
I thought the general rule is "use it if you want but don't blame David" :)
I didn't look at that package, but since the general rule for `xspace` is "Don't use it"[^1] I'm quite wary of `xpunctuate`, tbh. Have you taken a closer look at it, yet, and can give an educated guess whether it inherits the problems of `xspace`? [^1]: Citation needed, but David's take on it nowadays.
you know that you can create a backup key in your profile that you can then store in a password manager or something?
Didn't receive notification for this. Also, have lost my account again. :cry: Hopefully Joseph merges it back.
I used to get emails for new messages which would ping me. That's currently not working for me.
Since a couple of days I don't get email notifications for new chat messages. Is this a problem on my end or can somebody confirm the problem?
Marmot was the inspiration for writing the TikZmarmots package, but I'm the author of the package.
I know that, you are the author of the TikZmarmots package. marmotghost (marmot) is also an author of the TikZmarmots package. Is that true?
> Getting mythology wrong is my Hercules ankle. from https://twitter.com/OFalafel/status/1445451618728611843
Nice find! I like that they use the TeX lion as example image in the documentation!

In English, it sounds like my current age bracket: I am in my forties, and that's how it is pronounced