... and rabbits will just dig a burrow between the fast code and the good code :P
Most of the time it makes no odds - I switch to release if it seems relevant (it's just a drop-down in my editor, so it's easy)
Haha, three things and I failed to understand it yesterday. 1) It is more common for me to say "not me" than "not I". 2) Funnily, the font at my home system has a confusing shape for `I` that resembles with `|`. So I thought `| ↑↑↑` is a mathematical notation. 3) Wikipedia said that `↑↑↑` is Knuth's way of marking long integers (making it worse for me). Maybe I was too sleepy yesterday.. :joy:
Worst thing to ask for is an explanation for the joke, but not familiar with the notation, so I pass on this :P
sorry to disappoint you, but when I'm answering questions I don't use `-dev`.
Yeah, even I need it for my release, so I was wondering if I should release and then ask people to use dev or wait till it gets released, but since it is very close I will release my software :)
Oh yess! Sorry, I misunderstood that the date was of the publication of the news and didn't check it.
Of course, the 'project and friends' are all running dev anyway :-)
The pattern is nominally 06-01 and 11-01, but it depends on how busy I am the day before
When will the changes from [ltnews42](https://mirrors.ctan.org/macros/latex-dev/base/ltnews42.pdf) be public? Is there any predictable pattern to when do -dev formats become the usual generic ones?
For cheese fans: https://stockage.framapiaf.org/framapiaf/media_attachments/files/115/418/448/006/755/147/original/5ec1666292a73bc1.jpg
Yes, it's more robust to provide a setup macro, which is why most modern packages do that. Parsing key=value options is problematic, even if you use the new mechanism of the raw options list (as do `\ProcessKeyOptions`, `expkv-opt`, and `scrbase`) everything passed there has to survive a round of `\zap@space` (since the zapped list will still be assigned). Expansion control might help with that (in `\ProcessKeyOptions`-using lists you can use `key:c = macro` instead of `key = \macro` to pass in `\macro` without that being fully expanded in the zapping list, similarly in `expkv-opt`-parsing you can use `c: key = macro` to achieve the same -- unfortunately `l3keys` doesn't use the same syntax as `expkv`)
Thanks for sharing. It is difficult for me to stand the mix of `@`s and `_`s now.. :smile:
I didn't find an example in the wild, but with some experimentation, I figured out how the option works :) https://github.com/josephwright/ltx-talk/pull/102/files
Since there are known problems in key-values for `\usepackage` (i.e., `zap@space`), should modern packages rely less on package options? In my recent package bundle, I have a key-processing command that takes care of the local as well as global options. I did it when I didn't know the problems caused by `\zap@space`. Turns out that it is safer in general. Should/could this be a strategy for package writing?
 ^^^ I think what they need is the `\lens` macro from [pst-optic](https://ctan.org/pkg/pst-optic) :)
A good soul on mastodon shared this -- didn't have to dig this up :)
Wow! How do you have time to dig up all these goodies and still get any "real work" done?
"You Have Been LaTeXpOsEd: A Systematic Analysis of Information Leakage in Preprint Archives Using Large Language Models" https://arxiv.org/abs/2510.03761
If one can be allergic to `\LaTeX`, maybe I have a ms word allergy? Just in case, I think there should be warning signs on books etc. if they were written in word :P
I mostly solved the overlay package problem: instead of the package, I'm now only loading it via `\usetikzlibrary{overlay-beamer-styles}` and for the doc, I've create various texdoc aliases :)***y**et **a**nother **g**rand **u**nified **sy**mbol **lo**ader* doesn't sound to hard to remember :P At least it's not the beamer overlay awareness package for Ti*k*Z `boas`, `obas`, `abos`, `aosb`, `aobs`, `oasb` or whatever.
 The new [`panda`](https://ctan.org/pkg/panda) package currently makes its way around the ctan mirrors. Many thanks in particular to @Skillmon for all their helpful answers here!
With such a recommendation, the videos are directly climbing to the top of my to-be-watched-list :D