If I was mean, I would downvote twice....

@UlrikeFischer I suspect Bruno will have a better fix at some stage: I went for brute force

tug.org/TUGboat/…

@JosephWright oh

@PauloCereda texdev.net/2018/10/20/tugboat-goes-almost-open-access

@JosephWright ooh

@JosephWright a fast and working fix was certainly important here. Errors in four independent documents in a few hours after the release didn't sound good.

@UlrikeFischer Sure: I was pretty sure from the first report about where the bug was, in general terms

Das Pokémon

@JosephWright Me too, at least in very general terms: "Imho somewhere in the message break/wrap." ;-).

@UlrikeFischer Yes: I was pretty sure it wasn't the message system

So, everyone reading TUGboat this morning?

@JosephWright I was reading what I wrote. :)

@PauloCereda Is it good? ;)

@JosephWright is it online?

@JosephWright oh no :)

@UlrikeFischer See my links earlier: the board have made everything except the current issue open access

@JosephWright Yes, I read this but I didn't realize that it also meant that there is a new one.

@UlrikeFischer I'm not sure when 39:3 is out (@barbarabeeton?)

@JosephWright I just checked in the member area -- it isn't there yet, but now I wonder if I got the print of 39:2.

@UlrikeFischer Not sure if I have yet, to be honest

@JosephWright is "Next meeting -- Two weeks" still planed?

@PauloCereda Can I specify a root document for arara?

@JohnDorian files probably. :)

I might need more context. :)

@PauloCereda I mean something like % arara: % !TeX root = main.tex (forgive me the syntex) which would redirect arara to compile main.tex

@JohnDorian % arara: pdflatex: { files: [ main.tex ] }

That's the only thing I can think. :)

@PauloCereda Thank you, I will read about this in the documentation. I didn't know what to search for in the doc.

@JohnDorian Neither do I. :)

@JohnDorian Technically it's not a root document, we are just telling arara to compile other file instead of the current one. :)

Just bear in mind that %!TeX root = main.tex will make your editor run the compilation on that file...

@PauloCereda Could I also do %arara: arara: { files: [main.tex] } ?

@JohnDorian You could, provided that you have an arara rule, which we do not officially have. :) But I don't see the need for that.

@PauloCereda I am just trying to get used to vim, so currently I don't have %!TeX root functionality yet. I am rather trying to emulate it.

I was just able to make a shortcut for compiling the active document with arara.

Cool!

@PauloCereda What is your preferred way to compile main.tex when you are just editing chapter1.tex in vim?

@JohnDorian I usually have tmux and issue a direct compilation. :)

@PauloCereda open the file in emacs and type C-c C-c ?

/cat

@cis as you can see on the right, I'm the only monochrome human here this morning.

@PauloCereda I bought a new plughole stopper ^^^^

@UlrikeFischer ooh :)

@JohnDorian I usually use GNU make for LaTeX, so in my VIM it's just :!make with the current working directory the one containing the Makefile. Maybe you could as well write a VIM command that runs arara on the .tex file it finds in the current working directory (provided that you have a clean folder structure with only the main TeX file in the top folder and all others in subfolders)

@JohnDorian or you could create an option to set the current main file in VIM and use a modeline to set it (so something like % vim: texMainFile main.tex), but I'm not sure how this works (never needed such things)

@StefanKottwitz First when I read your question, I was like "huh, doesn't HE know THAT", and then when I read your answer I became very happy! It is very generous to make the recent issues available so quickly!

@mickep I had to post as a question here ;-) I hope for additional TUGboat readers when occasional TeX.SE users stumble across that information. And we could show more TUG presence here.

Is there a pgfmath function like \ifisstring?

@marmot temporarily accepting an answer would have also work, but it seems to be too late now unless you are going to offer a bounty for a second chance :)

@UlrikeFischer I'm pretty sure I did not yet get the printed copy of 39:2

@JosephWright \zap@space not the best idea ever :(

@UlrikeFischer Please be careful not to hurt the duck with heavy pots or pans!

@samcarter carefully lift the duck into the pan

@DavidCarlisle looks so ;-).

@UlrikeFischer the whole spec for the package handling code was that \docuemntstyle[array , longtable ]{artcle} shouldn't give file not found errors on " longtable .sty" , processing of key=value wasn't considered at all.... (but I'd already had to provide a patched version to Sebastian for hyperref within a year, we should have been braver then, I susepct)

@samcarter Good idea but perhaps the score is not that important. ;-)

@DavidCarlisle yes. Your code seems to work fine. I tried a bit also with KOMA.

@UlrikeFischer I'll probably open a public issue and post it there before adding

@DavidCarlisle Couldn't we just use the code from \tl_trim_spaces:n - does the same job at the ends of material

@JosephWright oh you mean not use zap@space and not need a second list?

@DavidCarlisle Yes :)

@DavidCarlisle I guess it comes down to how much change one feels is acceptable

@DavidCarlisle I'll mail the list

@JosephWright we could although I think last time I looked at this there were issues with expansion, but it makes sense, yes

@DavidCarlisle I have put in a file and will it add at the begin of my documents.

@santimirandarp Fire away

@santimirandarp /me Quacks quizzically

@santimirandarp Did you follow all steps of this answer : tex.stackexchange.com/a/240247/121799

@santimirandarp Yes, Hollywood is no longer what it used to be. ;-)

@santimirandarp Maybe this answer: tex.stackexchange.com/a/240387/121799 then?

@santimirandarp No, there are two answers, one by @samcarter and one by @AlexG.

@santimirandarp I see two different answers.

@JosephWright -- thanks for your vote of confidence. (it's nice to be appreciated.) here's hoping we did the right thing.

@barbarabeeton I'm pretty sure you are: certainly looking at the UK-TUG membership, people join for 'supporting TeX' reasons

@JosephWright -- tugboat 39:3 is still being edited. there are a couple of really "tough" articles (demanding in the technical sense, and long, to boot), and i still have to write my editor's column. so it'll be another week before it's ready to go to the printer.

@barbarabeeton Ah, cool

@barbarabeeton Looking forward to it, as always

@UlrikeFischer -- tugboat 39:2 has taken an unusually long time to get printed, mailed, and delivered. i received the editor's copy on october 10 (from previous experience, it was expected more than a week earlier), but didn't get the regular mailing until october 17. that's really unusual, and we'll be checking with the printer to see if anything unusual caused the delay.

@StefanKottwitz -- a suggested edit (i'd rather you make it, if you agree -- i'm too obviously biased): instead of saying that "the tugboat is funded by member support", how about just "tug is funded by member support". (rationale -- as editor, i'm an unpaid volunteer, and will continue to be, even after i retire early next year from my day job; the only expense items for tugboat are printing, postage, and costs associated with hosting on the tug website.)

@barbarabeeton While I agree, the focus was on the TUGboat and so its funding by TUG members, on this direct connection, not so much on TUG funding, so I'm not sure.

tRolling. . . my name is lAurI. Coined by the Don. I love (La)TeX and MathjaX. As much as i hate them to pieces. Last time we talked, Knuth bore smite on his creations.

Well intent. And what an empire!

Yet short of hopes. He specifically lamented \loop.

I thought it was a creative masterpiece but, well, . . .

We talked about \forever.

@Psmith You are challenged.

\loop \else.

\sorry to stumble in. To see a news TUGroup devoted to what these \backslashes have keystruck is an attractive nuisance.

(I can stumble out too. 'Smatter of fact it's about time)

@Psmith Shut-up...