I am impatient with long descriptions, but I do find that in a minority of cases, the description does lead in to a distinction that I would not have intuited.

I try to reflect on that during long descriptions, particularly ones that are highly redundant with something I remember.

infosec.pub is pretty tolerant…

Might check out the Haskell layout rules.

Basically, when you leave out the ‘{’ then Haskell uses your intendation to insert ‘;}’ on later lines between the leading whitespace and the first token.

There some really old Haskell code out there that lines up the ‘{;}’ characters on the left under block-introduction keywords.

If you do have to do it, you can hit 1234 or any other 4 digits after the 911 and you will still be connected to emergency services.

Source: accidentally called 911 when trying to make an international call and not understanding when the phone system needed the 9 prefix (only for internal extensions).

I was told something similar by a physician. Do your sleep routine, and then try to sleep for about 30 minutes. If it doesn’t happen, get up, use the time, and try again after an hour.

Chameleon Linux: Changing Stripes Edition

A Distribution Named SUE

The other suggestions are probably better, but you can technically self-host Wire (from Wire Gmbh) but I’ve never done it successfully.

I primarily operate in strict standard compliance mode where I write against the shell specifications in the lastest Single Unix Specification and do not use a she-bang line since including one results in unspecified, implementation-defined behavior. Generally people seem to find this weird and annoying.

Sometimes I embrace using bash as a scripting language, and use one of the env-based she-bangs. In that case, I go whole-hog on bashisns. While I use zsh as my interactive shell, even I’m not mad enough to try to use it for scripts that need to run in more than one context (like other personal accounts/machines, even).

In ALL cases, use shellcheck and at least understand the diagnostics reported, even if you opt not to fix them. (I generally modify the script until I get a clean shellcheck run, but that can be quite involved… lists of files are pretty hard to deal with safely, actually.)