If these humans are too slow, the beavers have to do it themselves! https://www.theguardian.com/world/2025/feb/11/beavers-save-czech-taxpayers-by-flooding-ex-army-training-site
Woohoo!! It is thereeee :) :) I checked literally five minutes ago and it wasn't there. Yayy!
Well.. it is making me anxious. :joy: The software I released was on my mind for around 3 years. Now it's live, but it's invisible. But yeah, it's a part and parcel of the game! :smile:
Abut an hour on GH Actions - a bit longer if I have to do it on my laptop (2020 i7 MacBook Pro)
Now the same problem is happening to my package. I released it the day before yesterday. The files are visible in the archive, but the page isn't visible. Hopefully it fixes soon.
I think that would be a fish though for the cat. TeXStudio can easily tempt new users.
I bet the latex2e builds leave enough time to grow the coffee beans first :)
I normally appreciate a bit of compile time for a quick coffee run, but with the tcolorbox doc, I've already drunken my coffee before it is finished :P ``` Transcript written on tcolorbox.log. --------------------------------------------------------- SUCCESS Total: 1383.617 seconds ```
Sorry, my comment was completely misleading. I was talking about the lazy evaluation that is not possible in the case of dim/skip registers (e.g.: https://topanswers.xyz/tex?q=8089#a7707). Your comment regarding `tl`s sounded similar.
Unfortunately, yes. The amount of spam was one of the nuances when I had a publicly listed university email address.
Hahaha he was found by some algorithm. I deleted the email and kept the sender in the spammer list :D
Nonetheless, it's funny that Prof. van Duck got such a mail, shows how good of a job you're doing for that alter ego.
*Disclaimer: This is a description of the usual behaviour of predatory publishers, and not necessarily true for Lupine Publishers* These publishers write to all the researchers they can find that might (or might not) have any expertise or interest in the fields of one of their journals. They usually don't investigate that well (or else they'd have seen that Prof van Duck isn't a real person), and try to convince them to publish an article in one of their journals. Since they are an open access journal they charge high fees (and most universities have subsidies reserved for open access, so the researchers can pay those fees). Usually those fees are necessary to finance the work a serious journal needs to do (review process, editorial process, etc.), but predatory journals more often than not don't invest that money into such processes but keep it for profit. They are the worst of the scientific publishing world. That's why I said "I'd keep my distance". Whenever you're contacted by a journal in such a way, I'd take a look whether it's suspected to be a predatory journal, and if so *stay away!*
Yep, as I suspected, others seem to share my assessment: Lupine Publishers is listed on the list of potentially predatory publishers: https://beallslist.net/ I'd keep my distance.
The sender is:  .
 Prof. van Duck received this email (a month ago, I didn't see it because it went to the spam folder). Is it spam or is it serious?
I assume the fancy French Vanilla Coffee box in the fridge represents TeXstudio :P
and of course the VIM cucumber is the prettiest and comes with its stern still attached.
?! Of course you can later change dimensions, and of course you can write an accessor function: `\dim_new:N \l_my_tmp_dim \dim_set:Nn \l_my_tmp_dim { 50pt } \NewExpandableDocumentCommand \MyTmpDim {} { \dim_use:N \l_my_tmp_dim } \dim_set:Nn \l_my_tmp_dim { 60pt } \MyTmpDim`
Hmm.. I have this complaint about some other registers like `dim` etc. too. There is no way to compute them dynamically. They are set at the time of definition and then there is no way back.
Oh no :( Okay... I will have to define control sequences that will do the same thing. Thanks for the hints.
Though arguably a design mistake in `expl3`, you're correct, a `tl` is always expandable.
Your `\tmptl` would only print the value of `\g_pkg_tmp_tl` when it was defined, not the current value, which seems like a strange interface. If that's what you indeed want your code is fine, otherwise you should use a level of indirection.