@JosephWright I guess it would be fine to just swap out every @opt@\@currname.\@currext with @raw@opt@\@currname.\@currext.

@Skillmon that was my thought last night as well but it was too late to be thinking about option handling:-)

@Skillmon I'll take a look later today

@JosephWright ooh pizza Saturday

@PauloCereda ham and pineapple please

@DavidCarlisle ooh

@PauloCereda after breakfast of course

@DavidCarlisle oh no

In LaTeX the aux files are read in twice: At the beginning of the LaTex run, the aux files that were created during the previous LaTeX run. At the end of the LaTeX run, the aux files created during the current LaTeX run. Does the LaTeX2e kernel provide a routine for branching depending on whether reading in at the beginning or reading in at the end of the LaTeX run?

This would be useful if you have things done via the aux files at the begin of the LaTeX-run but don't need them to be done once more at the end of the LaTeX run, and vice versa, for example. I branch for this purpose by having tested whether \@newl@bel is equal to \@testdef. I wonder if there are documented macros for users to do this by now.

@UlrichDiez you might also want to check \if@tempswa to distiguish \include usage, but otherwise \ifx\@testdef is all there is I think

@JosephWright while your at it: Maybe also change \PassOptionsToPackage etc. to go through the new mechanism if \ProcessKeyOptions was used. And please, give me some way to hack into it :P

@JosephWright I'd like to create a PR for the option parsing. (it would add the possibility for other packages to also benefit from the new parsing mechanism -- if you want I can also tackle the raw vs zapped issue in it)

@Skillmon \PassOptionsToPackage does already add to both opt@ and raw@opt@ doesn't it?

@DavidCarlisle yes, I meant that it should pass its stuff to the parser if the package was already loaded.

@Skillmon oh so works for later \usepackage that just run the key settings?

ooh

@PauloCereda a tutorial for picture mode?

@samcarter ooh

I doing a bulk compile with latexmk, and TeX got stuck. Is there some way I can interactively ask it what file it's working on?

@DavidCarlisle yes, essentially, a \PassOptionsToPackage should be the same as a second \usepackage call once the package was already loaded if it uses the new mechanism.

@PauloCereda counter-ooh!

@DavidCarlisle Sigh ... tex.stackexchange.com/questions/648195/…

@Skillmon Allowing the new approach to work with other keyval packages will need discussion - certainly not happening until the Fall release

@JosephWright ;-)

@JosephWright well, I can as well redefine \@onefilewithoptions@clashchk, but that feels very hacky. What I'm asking is pretty simple (and allows other packages to chime in): Instead of storing the family in opt@fam@ store the action in a macro.

@JosephWright yes I was out, just saw that

@JosephWright I thought we were just picking up unused option warnings when options were used with values. but that's showing 10pt which seems surprising

@DavidCarlisle the code adds every key it doesn't know. But I don't understand the logic. Why is the code extending the list with \clist_put_right:Nn \@unusedoptionlist {#1}? Shouldn't is only shorten it?

@JosephWright you got mail.