6:15 AM
@PauloCereda oooh...

7:05 AM
@UlrikeFischer Cool! tlgs applies off-release patches.

@AlexG I got it already this morning. My first example works again. My testfiles fail but only because the producer changed ;-).

@UlrikeFischer I need to dig out my old laptop and test myself with w32tl

2 hours later…
9:19 AM
@samcarter_looks_forward_TUG'21 the newest version of the figchild package avoids all the name clashes, it uses now e.g. \fcSheep.

@UlrikeFischer Oh, great! Thanks for letting me know!

9:34 AM
@samcarter_looks_forward_TUG'21 I only saw it by chance, I guess someone told them about the clashes.

9:48 AM
@UlrikeFischer I did not see a ctan announcement, maybe it is still in the 24h phase to distribute it to all mirrors

4 hours later…
1:54 PM
and today's question is: why is the LICENCE link at learnlatex.org/en/contact a binary download (and was it that way before) ? (@JosephWright)

@DavidCarlisle It's Not My Fault

@JosephWright blame @UlrikeFischer ?
@JosephWright I wonder if it works with LICENCE.md does that still trigger the licence icons in github? I might try on my fork...

@DavidCarlisle Worth a try, certainly

@JosephWright /home/texfaq.github.io/LICENSE.md and texfaq.org/LICENSE works, I think I'll try renaming the file at LL

@DavidCarlisle Cool

2:16 PM
@JosephWright still shows as CC-BY-SA in the github gui but rendered as text/html now with the site header. learnlatex.org/LICENSE

2:38 PM
Is there a standard answer we can point users towards regarding the problems with xelatex and pstricks because of the changes in ghostscript.

@daleif there is one regarding mac tex tex.stackexchange.com/a/591561/2388 but beside this, I don't think I saw one.

@UlrikeFischer wasn't there something about passing some option to xdvipdfmx

@daleif yes that is the other problem. But I don't think I saw a question about it yet.

@UlrikeFischer ok, then I've only seen it on texhax and the texlive list.

3:28 PM
@daleif -- This (tex.stackexchange.com/a/453786) is still about pstricks but it gives some details about Ghostscript. It was updated last month, so it's probably up to date.

3:41 PM
@DavidCarlisle quack

How do add a new line in a node? as in

\begin{tikzpicture}[remember picture, overlay]
\node<6>[xshift=-3.5cm, yshift=0.5cm] (b) [N]
at (current page.east)
{$\bm{f_{-a}}$ is the frequency array without the token $a$\\test};
\draw<6>[-Stealth, shorten <=1mm, shorten >=1mm, dashed]
(pic cs:bar) to [bend left] (b.south);
\end{tikzpicture}


@Anush if you specify a width for the node you can just us \\ , if you don't want to set a width, my go-to solution is often to use a tabular inside the node text.

@Skillmon thank you. where do I put the width? \node<6>[xshift=-3.5cm, yshift=0.5cm,width=4cm] (b) [N] doesn't work and nor does \begin{tikzpicture}[remember picture, overlay, width=4cm]
@Skillmon oh I see. text width. Thanks again

3:56 PM
@barbarabeeton I think Herbert Voss' answer on the TeXHax list if probably more relevant

@daleif -- Oh, I agree. But if you're looking for something in this forum, ...

There's no escape from escape.

4:41 PM

@PauloCereda Oh, the mole is cute :)

@samcarter_looks_forward_TUG'21 there's a duck date in progress in the background. :)

4:58 PM
@PauloCereda yeah, the straw must be difficult to use :)

@PauloCereda dinner

@DavidCarlisle oh no

6:04 PM
@PauloCereda XD

@Plergux :)

2 hours later…
8:06 PM
Does sed recognize a non-greedy *? Using *? gives an error. Is there a way to do that?

@AlanMunn Using sed -E seems to work: echo 'aaaaaaaaxxx' | sed -E 's/a*?x/b/'

@PhelypeOleinik Hmm. I'm using that and it gives me an error. This is BSD sed on the Mac, not GNU I guess.

@AlanMunn Hm, maybe. If I use --posix it no longer works (no error though)

@PhelypeOleinik Interesting, on my system (GNU sed 4.8) there is no error but it still matched greedy. (Even without --posix)

@PhelypeOleinik The workarounds given in the SO answers seem to do what I want, at least for the cases that might arise.

8:17 PM
@MarcelKrüger Without --posix it works (GNU sed 4.4)
@AlanMunn The workaround to a regex is another more complicated regex :)
@AlanMunn But searching for everything but the separator seems good indeed

@Anush I'm a bit late to the party, but anyways: tex.stackexchange.com/a/124114

@MarcelKrüger Of course in my last message to you I meant to say “For me only without --posix ...” (thus I assumed the extended regex is a GNU thing), but just typed half of it for whatever reason :P

8:37 PM
@TorbjørnT. -- That question looks quite good, Added it to the "often referenced questions" on meta. That section looks like yours. If you have any other candidates for the list, please consider adding them.

@barbarabeeton (Sorry, misread it as a suggestion to add it there, rather than you having done so.) But I'll try keeping it in mind, to add more there.

@TorbjørnT. -- Might help to answer some questions or identify duplicates more quickly.

8:55 PM
@DavidCarlisle In this case it actually might be the simpler route. Although I think that most of the non-greedy strings in the specific application will be delimited, so the "everything but the last delimiter" will suffice.

@JosephWright do you think we will/can maintain this or should we lose it? learnlatex.org/CHANGELOG

@DavidCarlisle :) The overly optimistic instructions for contributing suggested adding to this for every major change, something people clearly took very seriously.

@AlanMunn trouble is what's a major change? adding Catalan is major change for some people, less so for others. Changing the hosting server for running the examples was a major change just for me, probably.

@DavidCarlisle Yes, and I think that's why nobody actually knew what to do.
@DavidCarlisle Although change histories are very useful for software, I'm not sure how useful they are for something like learnlatex.
@DavidCarlisle I could see something like deciding to make all examples use lualatex rather than pdflatex would be a major change worth documenting. But "we added language X" isn't really major in the same way.

9:10 PM
@AlanMunn yes that was my thought too, and although we could maintain a change log of the changes to the software infrastructure supporting the site I'm not sure it's that interesting to other people.

@DavidCarlisle Yes, I agree. How the site works is relevant really only to the developers not the users.

9:45 PM
@DavidCarlisle Hmm, good question: probably drop it

10:06 PM
@JosephWright thanks, done.

11:03 PM
Grr. Some pandoc table markdown doesn't work on github it seems.