@barbarabeeton @Rmano Thanks for the tip with the rice! After a night in the rice box, the computer seems to be working, just the display is likely a lost cause. So no need to make a replacement in a rush and I can migrate all my stuff in an organised way.
@barbarabeeton The schedule for TUG'21 is really nice (at least from my European perspective)! I can get most session by attending lunch until night, so just shifting the whole cycle for a couple of days will be a lot easier than the alternating times from last year where a day of staying awake extra long was followed by getting up extra early. Very consistent schedule this year!
@samcarter_looks_forward_TUG'21 -- That's good news. It does seem biased a bit toward Europe. I.m a night owl, and the gap, from 21:00-03:00 is a disaster; anything before 07:00 is a lost cause. Sigh.
@CarLaTeX -- I'll try to repeat it a bit more often, gently. (If you feel too badgered, say so, please.) For now, think positively, step back, and keep a notepad close so you can write down ideas. You'll get there.
@JosephWright I would say it depends if you want to support the use case that people copy siunitx in an older texlive or not. I would probably more go for documentation, you could add some section "if you try to use with older texlive then ...".
@UlrikeFischer It's more the general point: we have a non-robust command uses as a 'character' in the input to a number; so far, this is the only one that's come up as an issue. I used to have an explicit setting for making things robust, but that felt quite awkward
@JosephWright given that it's robust in later latex, you could simply unconditionally make it robust, not really worth documenting an option that will become obsolete as people update latex
@PauloCereda A unified talk sounds fun! Let's alternate slides and see where this takes us. Looking forward to the session, it is nice to have all these interesting talks around my talk :)
