2 hours later…
7:18 AM
@Plergux hi! Good morning! We (Spain) got a volcano too! ;-) english.elpais.com/science-tech/2021-09-20/…

@Rmano Good morning! Impressive :D And born from the Atlantic Ridge same as ours :p

(although not one of the best pixar's short, I find the love<->lava thing a bit lousy)

Wow, that is so soppy! :þ
(I agree, it feels a little forced. Some of it was right out cringy, like putting the stress on "tinc" in "extinction" to make it fit into the music. Lame :p)

7:33 AM
I still think that the best is youtube.com/watch?v=JVJ2K1JNiJI

1 hour later…
8:41 AM
@Rmano Yeah, that one is brilliant. Simple concept with exceptional execution is often the best way to go :)

9:13 AM
quack

9:27 AM
4
^^^ from duolingo

9:47 AM
Good morning (I guess :) everyone,

In the last version of siunitx, isn't \l__siunitx_number_unit_product_tl defined?

since this answer https://tex.stackexchange.com/a/548367/2288 gets me this error of undefined control sequence.

@samcarter ^^^

@DavidCarlisle it is egreg who used an internal siunitx command ;-)

10:14 AM
@PauloCereda baa!

@Plergux awww <3

10:33 AM
@PauloCereda something for you to practice your French books.sayahna.org/html/sfn-french-poems-toc.html

@DavidCarlisle oh no

@PauloCereda ohh

@samcarter <3

@UlrikeFischer In case the Bär is looking for inspiration for his next carnival costume teddy-fabrik.de/Limited-Edition/Bear-Prominenz/…

2 hours later…
12:25 PM
@DavidCarlisle Sorry I wasn't here for a while. For issue is this for? We're definitely not gonna update any widespread packages in our TL21 at the moment. We basically only plan to update lipsum once a fix is out for the polyglossia incompatibility and we seem to be good to go very soon...
*What issue is this for?

12:45 PM
1

I am finding misaligned figure captions when using TeXlive 2021 with amsart. A test file is here: \documentclass{amsart} \begin{document} \hbox to\hsize{X\hfil \TeX{Live} 2021 on Mac\hfil X} \begin{figure}[h] \hbox to\hsize{X\hfil X\hfil X} \caption{XXXXX} \end{figure} \end{document} The first...

@yo' captions in amsart broken they will be fixed in latex-dev release today but that won't roll out for a full release for a month.

@DavidCarlisle oh goodness. If a fix in the core is needed, that's probably a no-no. We might mention it in our blog post though, I'll ping LianTze about this.

I'm just on mobile presently. it could be fixed in the class as i show there but we are changing the core so that fix not needed

@DavidCarlisle yeah I got it. This is somewhat unfortunate :( I'm afraid the only simple way to deal with it is by keeping the AMS templates on TeX Live 2020.

1:24 PM
@yo' you might want to take to latex team mail we could perhaps authorise you to add unskip to amsart

@DavidCarlisle that's a tricky thing internally...
@DavidCarlisle is it only that one change? Only amsart and not the other classes?

1:38 PM
@yo' probably the other ams classes as well (I could check) and of course potentially unknown other classes (which is one reason we decided to change the format (again) rather than change amsart.cls

@DavidCarlisle yeah, got it. I'll see what reply I get from the team (Eric, LianTze) about this one; we prefer not to touch the files much on texlive so we might really just decide to ask users to stick to TL20

@DavidCarlisle couldn't we add a firstaid for the current LaTeX?

@UlrikeFischer we could (one reason why I suggested they contact latex-team) but how soon would we need to get that to ctan before overleaf cutoff, or is it too late already @yo'

@DavidCarlisle We're basically done testing stuff, so we don't wanna make any significant changes. It's certainly too late to change the core. And even changing the ams classes might be a tricky one, that's still dozens of templates to test again

1 hour later…
3:12 PM
@yo' -- This would also affect amsbook and amsproc. Anything that comes out of amsclass.dtx.

@barbarabeeton ok thanks for letting me know. That's starts to get large-ish...

@yo' and @DavidCarlisle -- I've notified my AMS contact, ans suggested that he get in touch with David. If anyone other than AMS modifies the AMS-maintained packages, that's likely to foment trouble. It would be much better to try to work this out diplomatically. AMS will not give over control on maintenance of its document classes; certainly not as easily as it relinquished amsmath.

3:41 PM
@barbarabeeton for end users it's not too much of an issue they can use the fix I suggest in that answer, or they can use today's release of latex-dev (once it reached them) or they can use the next full release of latex in about a month. It's just that the last two of those options have just missed the cut at overleaf which is unfortunate but inevitable with any system (overleaf, texlive CD, ...) that takes annual snapshots at some arbitrary date

3:52 PM
@DavidCarlisle -- I do understand the scheduling complications. Email sent with more details.

1 hour later…
4:53 PM
@barbarabeeton ^^

Just gotta love the syntax-weirdness supported by Lua: print[[string]] is perfectly fine.

@Skillmon because tex syntax is so systematic and not weird at all

@DavidCarlisle exactly :)

@PauloCereda YIKES!

@Plergux it hurts! :)

5:03 PM
@PauloCereda only if you look at it.

@Skillmon exercising is dangerous

@PauloCereda I'm not allowed heavy lifting for a week, might rupture my spleen.

@Skillmon oh /hug

@PauloCereda aww, it knows it belongs in the bag for food.

@Skillmon I'm pretty sure it would hurt trying to use it O.o
@Skillmon LOL

5:09 PM
@PauloCereda you got a secret message

@Skillmon ooh

5:26 PM
@PauloCereda thanks, fixed

@StefanKottwitz Thank you <3

So, apparently ~ expands to \nobreakspace{}. a) What's the purpose of {} here, b) How is \nobreakspace different to \nobreak \space?

@Noldorin Definition of \nobreakspace: \leavevmode \nobreak \
Funny thing, the current implementation of \ekverr breaks ConTeXt.
\unprotect
\input expkv.tex
\protect

\starttext
\ekverr{ConTeXt}{gets broken}
\stoptext
^^^ This will drop you to some (seemingly) dysfunctional interactive TeX session.

@Skillmon Okay, thanks. I presume \  is identical to \space. What about the {} here?

@Noldorin no, \  is not just like \space, it is the primitive control space that isn't affected by \spacefactor (so isn't wider after a period, for instance).

5:41 PM
I see.

@Noldorin if you use ~ in a place where it gets expanded and then written to another file the {} make a difference (experiment with what happens if you change the definition and use the following minimal file: \documentclass{article}\begin{document}\tableofcontents\section{Foo~ Bar}\end{document}).
So compare the results of the code above to \documentclass{article}\def~{\nobreakspace}\begin{document}\tableofcontents\section{Foo~ Bar}\end{document}.

5:57 PM
Thanks. Can't test right now, but I presume one of them inserts an extra (breaking) space?

@Noldorin One of them gobbles the extra space after the ~, but only in the ToC.
Ok, found the reason why \ekverr breaks ConTeXt. For some reason ConTeXt doesn't throw an error when a short macro gets a \par as argument. ConTeXt is sometimes weird when coming from a strong LaTeX background.

2 hours later…
8:00 PM
@Skillmon luatex has a primitive that you can set to disable that error check

@DavidCarlisle yes, saw the same in the manual. I just find it strange to enable this by default.

@Skillmon oresumably they wanted to disable that and the primitive switch is a nod towards tex compatibility

8:13 PM
@Skillmon right, cheers