I just learned the hard way that evil things happen when you use \lstMakeShortInline to set ! as an inline delimiter and then use color mixing notation (e.g. blue!50) in a command. Took me about 30 minutes to debug.
@PauloCereda some of them are lovely. Like the one with the text LEVNÉ KYDY. It's in front of a bookstore called LEVNÉ KNIHY (CHEAP BOOKS) that mostly sells trash. And KYDY means RUBBISH or MUCK.
@HaraldHanche-Olsen Heh heh heh... I'm not a strong liquor person. I can just about manage beer. :p With one exception: Ardbeg whiskey. It's like drinking peat. Love it :p
@Plergux Ardbeg is good. So is Laphroaig. Even more peaty, I think? Re beer: I bottled 83 bottles of beer yesterday. Now they are all labeled and sitting in the basement to mature for a bit.
@HaraldHanche-Olsen I'm not sure we've tried Laphroig. We'll have to put it on our to-try list. The selection up here isn't very good whiskey wise, though the bigger stores have about six gazillion types of beer. :p Not that I'm complaining. What kind of beer is it that you make? I like sour, fruity, and malt beers the best. :)
@Plergux So far, mostly IPA and something like a light English ale. But lately, I have started experimenting with saison. Not quite the proper style, though: Traditional saison is a rather weak Belgian beer for use by farm workers in the summer. It is weak so they can drink a lot of it and still get work done. I make it stronger, and get no work done. 8-D
@PauloCereda The negative bottles are great for sobering up in a hurry
@Plergux My brother-in-law went to Belgium on a beer pilgrimage and came home with an armload of Westvleteren stout. I got to taste it. Now that's a beer!
Unfortunately, they make a very limited amount, and you have to go there in person to buy it.
@Plergux It would go flat. Better share a bottle with a friend or two. The bottles are not large, though. And I remembered it wrong: It's only 10.2%, even though it has “12” in its name.
@Plergux Have you tried cold brewed coffee? I haven't but I am curious. Basically, you just use a French press with cold water and let it sit overnight.
@HaraldHanche-Olsen Not cold brewed, but I've made my own iced coffee just making it regular, keeping it in the fridge for a bit and then put ice in it. :p I prefer things cold. :p
@PauloCereda heh heh heh... and greatly increases my chances of not sleeping. :p Not because of caffeine hyperactivity but because of caffeine indigestion :p (technically, I'm not even supposed to eat chocolate, but fat chance I'm gonna give that up. :p)
@DavidCarlisle The longtable side looks quite easy, you mainly has to store it in the multicolumn and again after it. I was now more wondering about the \text_purify side. It looks as there is a new "context" involved here. You don't want to remove all commands, only a few like \label and then store the string.
@Rmano I had to google that. :p These days I only see commercials on YouTube and at the movie theatre and I don't really use YouTube and it's been almost years since I've been to the movie theatre (too expensive :|).
@JosephWright I meant that one here wants to purify a text (removing e.g. a \label command and other problematic commands) but not in the same way as you want to do it if one wants to produce a pdf string. gettitlestring uses a similar method than pdfstringdef, but with a different set of commands.
@DavidCarlisle which probably means that one need to stick to gettitlestring for now. This here could work for longtable, but the caption package would need to adjust its code too (I'm not sure I understand what it is doing with longtable):
@UlrikeFischer thanks, not to mention caption package's ltcaption offspring.
@UlrikeFischer That's consistent with nameref now although I'm not convinced that gettitlestring is needed to be honest, it feels wrong to me. The original version just stored the original text then (like the setting of titles in toc or headings) can just locally define \label to \@gobble at the point it is used rather than trying to remove them at the point it is saved.
@UlrikeFischer yes I mean nameref shouldn't need it (it is a later addition, and I'm not convinced it's the right thing to do), although given where we are now, i agree doing the same in longtable is probably needed
@DavidCarlisle well the code says that the non-expanding version was used because of "feedback" (probably to many fragile stuff broke). But in view that much more commands are robust now, this is perhaps really no longer needed.
@DavidCarlisle I think you can simply use \def\@currentlabelname{...} and not pass through \GetTitleString, nameref disables the \label command anyway. But the code currently miss to use the optional argument of caption.
@egreg yes I realise it doesn't work but from a user perspective if you use \tag then auto-numbering is disabled so equation and equation* ought to be equivalent. but...
@egreg I know:-) As you may note I am not offering any solutions just saying that from a user view the current behaviour is sub-optimal. (Not that this is the the only thing in latex that could have that comment)
@DavidCarlisle Possibly, if hyperref disables the \refstepcounter and then, if no \tag is scanned, uses the same mechanism as for \tag to set the anchor with a suitable \refstepcounter. But…
@egreg fundamentally the \label /\refstepcounter system wasn't designed to have anchor nodes at specific positions, hyperref is just such a massive hack to get round that basic design mis-match.
@UlrikeFischer as @JosephWright just commented \begin{equation}[id=blub] would be easier to manage but currently the \label can be anywhere (as can \tag) so you really have no clue until the end.
@UlrikeFischer yes I'd started to make an answer based on trying to separate Hequation and equation counters but egreg's answer of using equation* is much simpler and better for the user (as an answer to his immediate problem). If you just want the unique identifiers using a global internal counter is certainly simpler, it depends if you mind if foo.pdf#equation.6 links to equation 4. destination names are not as visible in PDf as they are in HTML so perhaps that is Ok, but it is a bit weird.
@DavidCarlisle I was just writing "that you can't remove a destination" when I remembered that this package does it ;-). It doesn't work with xelatex currently, but I don't directly see a reason why it should'nt work with it too, imho it simply marks destinations with links as used in the aux.
@DavidCarlisle sounds as if you should move longtable 4.14 out of hiding
@Plergux well, I personally use Arch since years (and am very happy with it), but for my wife's laptop this seems like too much work (she isn't as computer-phile as I am, so won't maintain it herself)
@DavidCarlisle it seems to work fine already. I used it now and then (when I remembered to merge it), and I know from at least one large document using it too.
@UlrikeFischer yes I was being "cautious" in what I moved, so I think what is there is OK but it probably still leaves 20 year old bug reports unaddressed, i was hoping to find time to look through them again but perhaps I should just ship it as is...
@Skillmon Actually, one of the main reasons for using Manjaro for me is that I have the full package variety of Arch at hand while having very easy to use installation and driver selection (I had some trouble with that on Arch a few years ago and Manjaro's assistants really helped). I regularly recommend it to beginners.
@Skillmon Just a minor word of warning: Manjaro preinstalls some more software than the usual distro (e.g. Steam is pre-installed) which is aimed to help users but a cleanup of those programs (all visible in the start menu) might be a wise move after install.
@UlrikeFischer, @DavidCarlisle I'm still not quite sure what's needed for nameref: I think I've not been playing close enough attention. Any chance of a summary on the team list?
@JosephWright I'm not sure if anything is really needed. As @DavidCarlisle wrote somewhere, all this gettitlestring business is perhaps overdoing and it is enough if \nameref locally disables commands like \label.
@UlrikeFischer If I can keep tools packages not pulling in the the ho-tex stack that would be good if "required" still means anything, which it probably doesn't. I'll see what I can do...
@DavidCarlisle I think you can really try \def\@currentlabelname{caption text}. After all the text is normally written to the lot too, so it can't explode completly.
@Dr.ManuelKuehner Marmots and other *lings are still active on topanswers.xyz, though.... You can try there, if you don't mind preparing another question (well, just a bit of copy and paste)
@MarcelKrüger I just compiled in an empty folder and there it worked. Now I need to find which local file interferes.
@MarcelKrüger I don't understand it ;-(. They are using the same files, but the failing one is not showing the line Lua function luaul.restore_everyhbox = 11