@AlanMunn -- Well, that should make @DavidCarlisle less unhappy. Thank you. (But I still can't figure out how to make my laptop take a screenshot, especially one that's just part of the screen.)
@barbarabeeton If you're using Linux, most are supposed to support Shift-PrtSc for a specific region. If you're using Windows you have my deepest sympathies... :)
@AlanMunn -- No, not a Mac. I had a Macbook, and on that, I could manage screenshots. After an argument with the Macbook (I dropped it o my toe, doing much damage, but I also have an unresolved argument with Apple), I switched to a Dell with Ubuntu. For straight-up *nix, it mostly behaves nicely, but I haven't managed to conquer screen management.
@AlanMunn -- Where is PrtSc located? Hiding on an unmarked function key? (I had a Windows desktop when I was at the AMS, and after too many years of having important information garbled by conventions forced upon me by management, no way was I going to continue that.)
@AlanMunn -- Yes, the Macbook survived better than the toenail. And I think it still works, but never progressed past Snow Leopard. (I'm actually quite fond of those four-footed beasts. They're amazingly beautiful oversized pussycats. But definitely always a very secure barrier between them and me.)
@barbarabeeton suggestion: install ksnip (just use the .deb download). It's powerful and easy to use (especially with x11, with Wayland it's still a bit rough). github.com/ksnip/ksnip
@DavidCarlisle Do you happen to know if \xhookrightarrow[a+b+c]{1+2} in mathtools uses the extensible of 0x21AA if it exists, or what it does (I guess not, since we might not be in unicode math, but what if we are?)?
For those who maintain TeX Live 2023. There is a misleading CLOSE button that should be disabled during installation process. See the following screenshot. It is not intuitive for users.
@DavidCarlisle Really? Well, I guess the one in TL won't be updated equally regularly, but otherwise I see no problem in using the installed one. But there is no reason for jit anymore, as far as I have understood...
@DavidCarlisle I do not read it like that. "Also, "context" and "mtxrun" are symlinks to luametatex. The regular TL build does not create those either."
@DavidCarlisle Oops, that will break circuitikz build big ways. And I have no time now... I'll suspect I'll have to ditch the automatic context compatibility check...
@Rmano Why, though? Your travis file seems to explicitly install context (and TL) from Debian repos. So as long as Debian packages it, you should be fine, shouldn't you?
@mickep on the platforms its been built on, yes. but all the platform #defines have been stripped out. But Ken Brown (main cygwin tex maintainer) shown interest, perhaps he'll get it going, he probably knows all the "usual places" that system library calls fail
@TeXnician yes, the GitHub will still work, but not on my local machine where I use latest texlive (and often -dev) to check. Yes, I know, I just have to install context too, but I fear troubles...I'll see.