@DavidCarlisle Yes, that's not mentioned. The underscore and colon separators? The only mention is "LaTeX3 addresses this by renaming all the commands at the bottom layer."

Not sure what that means, though. Example?

@DavidCarlisle Don't even mention it :P

Can someone help my memory: What is the bottom of the page equivalent of \topskip?

@AlanMunn first world problems, I don't have a secondary monitor. :)

ooh a secret

@Skillmon There is no such thing on the engine level. For \raggedbottom etc. you typically adjust \topskip and then use the output routine to move the box up again.

@MarcelKrüger yeah, already took a look at that, one can use \@textbottom.

quack

@yo' twitter.com/AWDtwit/status/1363326827830202372

arara reached 300 stars on GitHub!

@PauloCereda ah!

@FaheemMitha I updated it with an expl3 example. The comment about latex3 refers to the original latex3 format (which pre-dates latex2e) where commands like \def or \hbox were not defined.

@DavidCarlisle OK, thanks.

@DavidCarlisle @JosephWright seen Karl's message about the updates?

@UlrikeFischer yes

Any English speakers around? Is one of these two spellings to be preferred? github.com/josephwright/beamer/pull/661/files github.com/josephwright/beamer/pull/662/files I can find both in the dictionary ...

EPOCH

@samcarter_waiting_for_summer British (double s) vs American (single s).

@samcarter_waiting_for_summer focused with one s is normal (a quick check of online dictionaries confirms ss is "irregular" spelling more common in the colonies

@DavidCarlisle focußed

@PauloCereda focuzzed

@UlrikeFischer ooh

@AlanMunn hmm en.wiktionary.org/wiki/focussed could be summarised as saying "use as many s as you like:-)

@UlrikeFischer could we just use the Greek puenc-greek.def and not have one at all?

@DavidCarlisle no, they don't overlap. The greek file defines a lot of additional commands, stuff like \accdialytikavaria and accents.

@DavidCarlisle I guess I was overgeneralizing the doubling rule. Because the doubling is British. I wouldn't use the double s in focused though.

@UlrikeFischer I know the Greek one is bigger but couldn't they be merged?

@DavidCarlisle @AlanMunn Thanks for your feedback! Any opinion on github.com/josephwright/beamer/pull/662/files ?

@samcarter_waiting_for_summer I wouldn't normally hyphenate rewrite

@DavidCarlisle actually they do overlap, I hadn't looked at the end. But I don't think that we want to load all these commands. The problem is that we need to load it for psdextra/math, but then we don't want tons of special greek accents and other commands).

@DavidCarlisle thanks!

@UlrikeFischer well actually the math is done via \let\alpha\textalpha but it doesn't have to be that way, it could be separated. But perhaps simplest is to keep the definitions we have and rename as you say, or make them like the cyrillic and inline them again with conditionals (not so keen on that)

@DavidCarlisle I would simply rename it, e.g. to pugreekenc.def.

@UlrikeFischer sure Ok that fixes the issue and probably the thing to do, I was just thinking it's a bit hard to document why there is pugreekenc.def and puenc-greek.def split that way a more rational split might be pu-math-greek, pu-greek-greek, pu-classical-greek, but probably the coordination effort isn't worth it, especially as we need to refactor hyperref anyway in other ways.

@DavidCarlisle yes probably it would make sense to sort this better, but I have no idea how much is really actually needed today. I suspect that quite a lot of the larger file could go (we didn't get any complains that we perhaps "hide" the file currently ...)

@UlrikeFischer yes just rename the file and keep everything as it is for now.

@UlrikeFischer here the greek-fontenc version is the one that wins:

@DavidCarlisle hm, we could also simply delete our puenc-greek.def and if someone complains about to many definitions, we can blame greek-fontenc ;-)

@UlrikeFischer that's what I meant with the first comment: that we could drop ours and use the other one (and ask that he adds anything that is missing

@DavidCarlisle ah sorry, I thought you meant to merge the greek-fontenc into hyperref, not the other way round. That is probably a quite good idea, the maintenance would then be in the language package.

@samcarter_waiting_for_summer -- I go along with @AlanMunn: double "ss" British; single "s" U.S. As for "rewrite", ordinarily no hyphen, and certainly so in this example.

@PhelypeOleinik after writing this comment I followed the link in the question to see where the code came from:-)

A cool set of tools for those of us who deal with a variety of different data formats: miller.readthedocs.io/en/latest/index.html

Is there an option for latexmk to give a summary of the files it has built/compiled at the end of the run?

So for example:

latexmk -pdf foo.tex bar.tex baz.tex

[...]Built foo.pdf bar.pdf baz.pdf

@DavidCarlisle You can't hold me accountable for what 2018 me said :)

@PhelypeOleinik I would never do such a thing, but my 1993 self said this and holds your 2018 self accountable: footnote{This is really a pre-release, to see whether people like the idea of a command like this. This implementation is \emph{not} particularly robust.

1993 @DavidCarlisle is mean :)

@DavidCarlisle I hope you are not trying to hold me accountable for not reading documentation :)

@PhelypeOleinik I was just wondering if you were below the age of criminal responsibility in 1993...

@DavidCarlisle Does not being born count as a crime?

@PhelypeOleinik no but it means I can blame your parents

@DavidCarlisle Oh, that sounds reasonable now :)

@DavidCarlisle that's mean

@DavidCarlisle oh

@PauloCereda I'm in need of a back dated not mean reference

@DavidCarlisle ooh hold on

1993 @DavidCarlisle is not mean :)

ooh

@DavidCarlisle That seems credible!

@PhelypeOleinik I'm sure 1993 @PauloCereda was a good judge of character

@DavidCarlisle :-)

@DavidCarlisle A young duckling. Not enough for dinner

@DavidCarlisle -- Hmmm.

@UlrikeFischer Enjoy the PR

@JosephWright I saw it, but I'm just trying to finish the last open points in the pdfmanagement, so I guess I will look only tomorrow.

@UlrikeFischer I'm not sure how to handle conversion for ICC-based spaces: just map them to DeviceGray/RGB/CMYK?

@UlrikeFischer Perhaps I should add support for the Alternative key? Then we can use that or fallback using the number of components?

@JosephWright that sounds sensible. Imho it is either like gray/rgb/cmyk or something that the user has to provide.

@PauloCereda arara is on hacker news!

@JosephWright Watching Ronnie vs. Jordon Brown?