@lanodan Suspended my laptop several times accidentally just by putting a phone between the keyboard and the hinge. I guess the first time was confusing, but then I started doing that occasionally on purpose :-)
@lanodan@kirby Intuitively, I thought that this would be mostly needed for nontrivial immediate values in the instructions. But now I am not sure: prefixes, instruction "name", up to four arguments (incl. weird addressing modes of x86_64), it might add up.
A quick disassembly of /bin/df shows that 9-byte instructions are rather common:
I think this is some security guard or sth; the last 4 bytes look like an imm32 value. I am not sure whether "full" 15-byte instruction exists, though…
(Looked at some AVX instructions, they take ~7 bytes. Maybe some horror like VEXTRACTF128 might be long, it has 3 arguments, idk)
@lanodan@piggo Whenever I use manpages, I use man -a and quickly skip from GNU pages to the POSIX ones. (For section 1, that is; OTOH system APIs often read better from Linux man-pages than from POSIX.)
I quite hate how GNU manpages mostly give the incantation for the actual documentation (Full documentation […] available locally via: info '(coreutils) ls invocation'). And for stuff like make(1), GNU manpage is pretty much a complete joke (lists only flags for the command, not the language).
But still for common invocations, I find tldr is usually quicker than the manpage.
@lanodan@piggotldr is priceless for the common magic incantations. I use it mostly for options to dig and sometimes rsync, but there are definitely many tools I only use rarely (join, paste come to mind)…
@hj@kaia@SuperDicq@magmaus3@mischievoustomato I find GIMP's UI a bit worse. I wouldn't classify using either as pain, but in Inkscape I imagine the sets of SVG objects and usually am able to do what I need. I can do a lot in GIMP too, but some things require tricky operations (like actually drawing a circle).
@lanodan I wouldn't probably support the code removal so directly. There is something to learn from the issue and it's not like there would not be vulnerable code on GitHub anyway (you can get e.g. Linux kernel v5.12-rc1-dontuse if you want). Imho the issue is not "someone could see the bad code", but "somebody could get it by mistake", at which point a better way would be ~making sure people can only download the code interactively and with seeing a big warning for some time.
But GitHub needs to be on good terms with their shareholders (not community), so it would make sense they would remove it preemptively. Also, if Jia got enough rights over the xz repo, they might have killed it themself, no GitHub employee involved.
@lanodan@chjara@alexia@thelettuceman Doesn't matter which one, as long as the results can be used "complete[ly] automatic[ally] […] to tell computers and humans apart", no? :-)
@kaia According to this article (Czech only, sorry), there should be an option for 50 more years. So we're safe :-)
The same article describes how Czechia has one lot permanently (if I read into it correctly) and that we are trying to exchange the two leased lots for another lot/s (there are too low bridges, so it is not very usable). The exchange could happen this year.
I didn't factcheck it, just remembered reading about this ~recently.
@Moon This actually happens to me quite often (EeePC T101MT). For me it seems to be related to hibernation and feels quite harmless, so looking into that is very low priority.
The only annoying thing is that this message gets to all my open terminal windows.
@lanodan For me it used to be some misspelling somewhere. And since that lead to repeated frustration, I went to fiddling with about:config quite fast to stop that.
But it is funny that the search bar *doesn't* mangle its contents on search lol.
@lanodan Also it made me mad that firefox would "autocorrect" the domain names, like .vom → .com, or try automatically adding www prefix. I think it used to do that even if the changed site didn't exist, so it only made things worse…
@lanodan@xianc78 Reminds me of a Linux class on machines that had console beep enabled. And even when nobody beeped intentionally, it was still rather silly.
@icedquinn@cinerion@lanodan Well, I haven't used it for my programs, my gripes are based on my experience with building Anki from PKGBUILD, and at that time it was a bit painful. I remember it leaving processes running after the build and maybe some other stuff, but in fairness it might have been partly because of a bad PKGBUILD. Sorry, didn't mean to hate Bazel in general…
@lanodan@icedquinn@cinerion I do not want to build Anki from source by hand, but Arch's [PKGBUILD](https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=anki) is quite capable (I don't understand some of tha funny stuff it does, though). At least it does not use Bazel as the build system anymore…
LEdoian here. I break/(ab)use computers. If there is a weird command I can run to break something, I will gladly run it.(I especially like git, systemd and fd.o standards.)Proud admin of my #Pleroma instance and sysadmin in general. I also know some stuff about computer networks.Grammatical gender: Masculine (He/His)Account is locked to deter bots and weird corporate accounts. I accept follows from random people if their account seems to be marginally legit (=human-like), I just don't want to be scraped (except for the public posts maybe).