drougge

9 ms·

1.
by drougge 6mo ago
Those that have some git status information in their shell prompts should probably make sure they are not bitten by the same git issues. I currently have to following (zsh syntax) setup for that: git=(git -c core.hooksPath=/dev&#x
2.
by drougge 8mo ago
Probably inspired by Vinum's "NO FUTURE" for destructive operations. (Vinum was a raid system used on older versions of FreeBSD.)
3.
by drougge 10mo ago
This seems interesting, but I got stuck fairly early on when I read "all 32,385 possible input combinations". There are two 8 bit numbers, 16 totally independent bits. That's 65_536 combinations. 32_285 is close to half that,
4.
by drougge 11mo ago
There's probably a lot of other memory bugs though. The first thing I looked at was the shell, and almost immediately I spotted an out of bounds write (input[n] = '\0' where n could be sizeof(input)).
5.
by drougge 11mo ago
The C= 1084S he uses is a more a (very good) PAL TV than a computer monitor, even if it was sold as a monitor. So "576i" in your terminology. (It was also sometimes sold with a TV tuner, or at least the earlier 1084 (same picture
6.
by drougge 11mo ago
Surely that 20+ year old CRT didn't run at more than 240Hz? Something other than framerate is at play here.
7.
by drougge 1y ago
I have a related complaint about modern consoles: They are frequently unreadable, because they just have to use all the pixels. I booted Debian (IIRC) on a laptop with a 13" 4K screen and got something like 426x135 characters. No chanc
8.
by drougge 1y ago
One thing that really annoys me about the HTTP standards is that some older version used to say that text/* without a declared charset was definitely latin-1 (don't remember which version exactly). Then a later version said no, te
9.
by drougge 1y ago
Using "#!sh" at the top of the file does work, but not predictably. It may execute sh in your current directory, which is what Linux does, but your shell may override that (zsh does if the first attempt fails). So it works, but no
10.
by drougge 2y ago
I think it's worth pointing out that the example in the article contains a bug caused by not having shadowing: "const foo3 = try foo.addFeatureB();" should not be using the original foo, but foo2.
11.
by drougge 2y ago
I have now found the documentation for ExecStop (in systemd.service(5)), which hopefully improves my understanding. It definitely seems to be both "cause to stop" and "after (unexpected) stop" in one. You can look at $MA
12.
by drougge 2y ago
The name sounds like it means "this is how I want you to cause the service to stop" to me (and clearly to others as well). That would be symmetrical with ExecStart meaning "this is how I want you to cause the service to start
13.
by drougge 2y ago
VGA is much easier to produce, and the RP2040 can do 1280x1024@60 no problem. The official examples use several clock cycles per pixel (2 IIRC, but it might be even more), but you don't have to. I made half a terminal with that output,
14.
by drougge 3y ago
I have felt for a long time that this half closed state was a mistake. It fails to match naive expectations and can be hard to handle correctly even if you know about it. And as far as I can see there is no real benefit to having it. Is the
15.
by drougge 3y ago
I consider myself an old unix person, but I use dc. Possibly to make it more confusing to anyone who looks at what I'm doing. It also gives the math result here of course. % dc 9999999999999999.0 9999999999999998.0 - p 1.0 %
16.
by drougge 3y ago
If you're using a somewhat modern shell there is $RANDOM which gives you a 15 bit random number. So e.g. sleep $((RANDOM / 546)) but I guess most cron jobs run with an extremely conservative shell that might not have it.
17.
by drougge 3y ago
These modern useless scrollbars really anger me. I can theme some things (unless some modern packaging tech makes the app ignore my theme), I can make the ones in Firefox usable but ugly (with widget.gtk.overlay-scrollbars.enabled and widge
18.
by drougge 3y ago
His mention of Google also links to DDG, so I think it's all intentional. Possibly because the modern word for searching the internet is "to google".
19.
by drougge 3y ago
I'm someone who likes to use fork() and then actually use both processes as they are, with shared copy-on-write memory. I'm happy to use it on things consuming much more than 100MB of memory. In fact that's where I like it th
20.
by drougge 4y ago
Part of the problem is probably that termcap uses : as a separator between capabilities. There is \C for colon, but there are implementations that don't support it. If nothing else I know the termcap[info] command in screen doesn'
21.
by drougge 4y ago
Colon is the correct separator there. Semicolon separates different instructions, a group of values that is a single instruction is colon separated. For example \e[38:5:196;1m specifies red and bold. Using ";" is popular, and some