The schedule for the TUG'23 conference is online: tug.org/tug2023/program.html!

@barbarabeeton I will miss your talk. :(

@mickep Probably same here. And the Tikzlings talk too. If I don't want to start my journey at 4am :D

@TeXnician 4am sounds a bit tough. I go with the night train to Hamburg. Could have booked one day earlier perhaps, but too late now.

@TeXnician will you stay at the same place as the Brazilian?

@mickep Same here, I also pondered whether to go one day earlier but now my booking is for Friday. Still flexible on trains in the morning but it's still a 4 hour trip from here to Bonn.

@mickep Yes, I will :)

@TeXnician Very good!

@mickep -- At that hour, I may miss it too, at least brain-wise. I'll still be "set" at 03:30.

@barbarabeeton ohh. I hope you stay at the hotel where the conference is at least.

@mickep -- Yes, that's where we're registered. I'm hoping most participants will be there. (It's hard for non-TeXies to be surrounded by us.)

@barbarabeeton I won't ...

I read the carriage return character (ASC 13) is catcode 5 by default. Does the line feed character (ASC 10) have any special catcode, or is it just lumped with "other"?

On pg 114 of "TeX by Topic" is written:

> Explanation: the delimiter between parameters 1 and 2 is a space of category 10. In between a and b there is a space of category 12; the first space of category 10 is the space that is generated by the line end.

I'm wondering if this is a typo, and it should be "between b and c".

("TeX by Topic" is part of TeX Live. texdoc texbytopic.)

I could post more context.

@FaheemMitha yep, ASCII 10 is category 12 in LaTeX and plain TeX. You could check this yourself, just use \showthe\catcode10 in your file and the answer pops up in your log.

@Skillmon Oh. I didn't think of doing that.

I suppose the carriage return has its own catcode for historical reasons?

If someone would confirm the typo, I could report it to github.com/VictorEijkhout/tex-by-topic, which might be an official repository (I'm not sure).

@FaheemMitha Carriage return doesn't have a catcode. End of line has a catcode (5) which so happens to be set to <return>. Not the same thing.

@FaheemMitha It does look like a typo.

@AlanMunn Oh. I was just quoting overleaf.com/learn/latex/Table_of_TeX_category_codes.

5	End of line	ASCII code 13 (\r)

ASC 13 is carriage return.

@AlanMunn OK. Should I report it to that GitHub repos? I'll check if it's in the current version or not. I tried to search the document online but it didn't work for some reason. So I guess I need to clone.

I followed the instructions to do make onepass pdf, but it crashed with:

cp: cannot stat '/home/faheem/Projects/TeX/bib/tex.bib': No such file or directory

The error is still there in the version online. I guess I'll post an issue and hope somebody sees it.

github.com/VictorEijkhout/tex-by-topic/issues/1

It's a bit surprising that there are no other issues, but it looks like the repos is new. I hope it is actually being used, and not abandoned, and somebody sees it.

Can anyone comment about the build issue?

Also, a bit later in that same example is the following:

> In between a and b there is a space of category 12; the first space of category 10 is the space that is generated by the line end.

What does he mean by "space that is generated by the line end"? I'm a bit fuzzy about this, but isn't the line end category 5?

@FaheemMitha Others can explain this better than me. See tex.stackexchange.com/q/7453/2693 for the full story.

@AlanMunn Ah, yes. I thought it might be something like that. I recalled that TeX converts a line return into \par, but apparently this depends on the state as well. The usual TeX rabbit hole. Also, I had the impression that conversion happened "later".

@Rmano -- Thanks for your update to the question on \vdots. I'll just remind you, and everyone else, that there's a meta "question" to help find duplicates or related info -- Often referenced questions. Whenever I see a post suggesting a duplicate, and it looks really good, I check to see if it's listed, and if not, add it, I do this almost indecently often, and the organization probably isn't ideal. Suggestions welcome.

@barbarabeeton An impressive list.

@FaheemMitha -- I can't take credit for starting it, but I find it useful, much better than my memory, so it's worth maintaining. It's gotten so large that it's getting hard to find things. All suggestions for improvements along those lines cheerfully considered. (I'll actually be using some of the categories as a basis for my talk at the TUG meeting.)

@barbarabeeton These days it seems fashionable to start babbling on about AI, but I won't do that.

For one thing, AI isn't actually AI.

@FaheemMitha -- True enough. And I've now seen some "answers" from the "AI" chatbots that are so erroneous that I don't want to trust anything created by one of them without checking.

@barbarabeeton Perhaps the Meta link would be better at the top? Or maybe the bottom?

@FaheemMitha -- That question has been added to frequently enough that it's usually near the top of the meta list, but mere users can't affect the page. Possible question for our moderators. Maybe an entry in the tex.sx "welcome" message, to say it's there.

@barbarabeeton To be clear, I'm talking about the link "Meta TeX.SE" in the list at the beginning of the question Often referenced questions. Which says Community Wiki.

@barbarabeeton I know of the existence of that (impressive) list, but it's true that it should be listed somewhere in a more prominent way, although I don't know how...

That link is two thirds of the way down. It feels like something that should be a bit separate from the general list.

Yes, it looks like it is generally editable.

@FaheemMitha -- It's "Community wiki", so anybody can edit it. I suppose a mod could tag it "featured" so it would appear on the main q&a page, but the overall arrangement of these pages is in the control of the "powers", and they often don't agree with the inhabitants of the individual .sx sites, as we've learned.

@JosephWright -- For the first time that I can remember, I find in the meta review queue a proposed edit to a tag wiki: tex.meta.stackexchange.com/review/suggested-edits It looks like it's trying to add two email addresses, which makes no sense. There's no context, and figuring out how to look at the existing tag wiki text isn't trivial. So I thought I'd ask for a mod opinion, and will ignore it myself. (Thanks. Sorry to bother you.)