oh, thanks for the clarification. I wasn't aware that it adapts the considered category code of the colon.
I just realised what the biggest advantage of ext.beamer is: I no longer need to remember if it is overlay-beamer-styles or beamer-overlay-styles :) [I had a similar problem with opening the doc, but I solved it by defining `abos`, `oabs`, etc. as texdoc alias of `aobs`]
A hungry duck: 
Thanks, can you explain why the doi link works and the ctan one doesn't?
But why does it work with the other link I have shared (the DOI one)? Hehe, okay. I will keep this in mind for the next time..
you could load the PDF management and then use `\hrefurl`, this will force the link type and not rely on hyperref guessing it: ~~~~ \DocumentMetadata{} \documentclass{article} \usepackage[colorlinks]{hyperref} \ExplSyntaxOn \def\testpkg#1{% \edef\tmppkg{https://ctan.org/pkg/#1}% \hrefurl{\tmppkg}{\tmppkg}% } \ExplSyntaxOff \begin{document} \href{https://ctan.org/pkg/hyperref}% {https://ctan.org/pkg/hyperref} \testpkg{hyperref} \end{document} ~~~~
no `\href` supports also catcode 11, a direct `\href` inside `\ExplSyntaxOn` works https://github.com/latex3/hyperref/issues/381 But it needs a chance to adapt catcodes before the argument is used, as it is a sort of light-weight verbatim command that must also be able to handle # and %. So at soon as you pass to it an argument whose catcodes are frozen this breaks.
In case somebody is interested in font licensing: https://fontlicensingmess.com/introduction/
The problem is that `\href` searches for the `:` but only supports it as a category 12 token, hence you get the error, and can use `\c_colon_str` to work around it. The fact that this is already an existing question on TeX.SX (though I didn't search for it, so I can't provide a link) tells you that there were at least two people having that issue, which warrants a question to build a knowledge base :P
1. I thought it's a small issue not worth a separate question. 2. Ahh, okay, I did `\ExplSyntaxOff <code> \...On` and it worked.
1. you could've asked a question (though this is already an existing question on TeX.SX) 2. What @Qrr meant was something like this: ``` \documentclass{article} \usepackage[colorlinks]{hyperref} \ExplSyntaxOn % uncomment for two surprises \def\testtex#1{% \edef\tmppkg{https\c_colon_str//ctan.org/pkg/#1}% \href{\tmppkg}{\tmppkg}% } \def\testdoi#1{% \edef\tmppkg{https\c_colon_str//dx.doi.org/#1}% \href{\tmppkg}{\tmppkg}% } \ExplSyntaxOff \begin{document} \testtex{hyperref} \testdoi{10.1016} \end{document} ```
Uh oohh! But, what about this then: ``` \documentclass{article} \usepackage[colorlinks]{hyperref} % \ExplSyntaxOn % uncomment for two surprises \def\testtex#1{% \edef\tmppkg{https://ctan.org/pkg/#1}% \href{\tmppkg}{\tmppkg}% } \def\testdoi#1{% \edef\tmppkg{https://dx.doi.org/#1}% \href{\tmppkg}{\tmppkg}% } \ExplSyntaxOff \begin{document} \testtex{hyperref} \testdoi{10.1016} \end{document} ``` ?
``` \documentclass{article} \usepackage[colorlinks]{hyperref} % \ExplSyntaxOn % uncomment for a surprise \def\testpkg#1{% \edef\tmppkg{https://ctan.org/pkg/#1}% \href{\tmppkg}{\tmppkg}% } \ExplSyntaxOff \begin{document} \href{https://ctan.org/pkg/hyperref}% {https://ctan.org/pkg/hyperref} \testpkg{hyperref} \end{document} ```
Is there any difference between: ``` \tl_set:Nn \l_tmpa_tl { foo } \tl_set:Nn \l_tmpb_tl { bar } \tl_set_eq:NN \l_tmpa_tl \l_tmpb_tl ``` and ``` \tl_set:Nn \l_tmpa_tl { foo } \tl_set:Nn \l_tmpb_tl { bar } \tl_set:NV \l_tmpa_tl \l_tmpb_tl ``` ?
I've been fighting with my git client for half an hour. The moment I start to create a reproducible example, the problem magically disappears, not only in the MRE but also in the actual repository. Lesson of the day: Rubber duck debugging always works!

Fantastic news from TUG, Barbara is now officially a wizard! https://fosstodon.org/@TeXUsersGroup@techhub.social/114383008207345367
Oh, look at this shiny new beamer toy! https://github.com/Qrrbrbirlbel/tikz-extensions/releases/tag/0.6.1
@samcarter is this ok or something you want changed? https://github.com/Skillmon/ltx_xistercian/commit/ec817793ec4bf7fbb5ca04360c76a5bb00fcc143
It's not my language, but a neighboring language and we share the script except some small differences. So we visually look similar. My language is Marathi which is there in the learnlatex ethos [from a long time](https://www.learnlatex.org/mr).
Physics tackling the really important questions: https://pubs.aip.org/aip/pof/article-abstract/37/4/043332/3342795/Pour-over-coffee-Mixing-by-a-water-jet-impinging
Yupp, I don't think Ti*k*Z needs a separate command, or even if it does, it's just `\def\tikzlogo{Ti\textit{k}Z}`.
If you ask a question I could show you some code (might take until tomorrow, travelling atm)
Lovely! This probably should be a question and an answwer for reference.
Tikzmarks, I've happened to have done that just yesterday https://raw.githubusercontent.com/samcarter/samcarter/main/ressouces/Dante2025_Cookies.pdf
[`hologo`](https://ctan.org/pkg/hologo), [`metalogox`](https://ctan.org/pkg/metalogox).
Is there a way to uncover a code snippet line by line in beamer with minted?
There are built-in macros to render TeX (`\TeX`) and LaTeX (`\LaTeX`), right? Are there similar macros for other names? Like TIkZ and metafont?
Wait, who forgets arguments? The occasional element separator might be left out, but entire arguments?
The arguments are at least consistent in minted and not some highlighted and some forgotten :)
:) I know. But arguments are also not highlighted in `minted` are they? I thought it only highlights the braces.
For LaTeX-stuff you don't necessarily need to define any keywords in `listings` as well: `keywordsprefix = \\` (untested, but should do)
... or use beamer with minted :P (for the moment, I'm quite happy with minted as I don't have to define any keywords etc.)