IMO the NUL-delimited options are by far the biggest win for shell scripting. $' ' will be the most commonly used addition, but "$(printf '...')" was always an option before. You don’t really have an alternative read -d ''.

Strange, I don’t see this behavior on my device. Not sure what information would be relevant to debugging this though.

That’s a latrine. They’re talking about a fancy light fixture.

Move the keyboard to the floor

*Thank you engineers who happen to be working at Facebook

Thought I’d check on the Linux source tree tar. zstd -19 vs lzma -9:

❯ ls -lh
total 1,6G
-rw-r--r-- 1 pmo pmo 1,4G Sep 13 22:16 linux-6.6-rc1.tar
-rw-r--r-- 1 pmo pmo 128M Sep 13 22:16 linux-6.6-rc1.tar.lzma
-rw-r--r-- 1 pmo pmo 138M Sep 13 22:16 linux-6.6-rc1.tar.zst

About +8% compared to lzma. Decompression time though:

zstd -d -k -T0 *.zst  0,68s user 0,46s system 162% cpu 0,700 total
lzma -d -k -T0 *.lzma  4,75s user 0,51s system 99% cpu 5,274 total

Yeah, I’m going with zstd all the way.

Video files are just a bunch of zip files in a trenchcoat.

It used to use project folders, but due to confusion/user error was changed in 3.0.

zstd or leave

I run my Nextcloud behind Tailscale, and Caddy handles theTailscale https certs.

That’s because it was a regression from 1.5 to 1.6 that got fixed.

The 10x speedup is in linking builtins during startup, so it’s only really seen for very small inputs.

I typically use find "$HOME/docs", but with a few caveats:

• In Zsh or Fish, the quotes are unnecessary: find $HOME/docs
• If I’m using anything potentially destructive: mv "${HOME:?}/bin" ...
• Of course, if it’s followed by a valid identifier character, I’ll add braces: "${basename}_$num.txt"
• I’m pretty inconsistent when globbing: "$HOME"/docs/* or "$HOME/docs/"* are common for me.
• I don’t use "${HOME}" unless I actually need the braces. The reason? I write more Zsh than anything, and the braces are even less necessary in Zsh: $#array[3] actually gets the length of the third element of the array, rather than substituting the number of arguments, then the string 'array[3]'

With embedded terminal escapes? True evil indeed.

Bryan Lunduke on /c/programmerhumor? Not what I expected, but okay.

Yeah, from the first line

Zsh, an extended version of the Bourne Shell (sh)

This screams AI-generated.

There are two massive points no one has mentioned yet.

• Quoting every expansion isn’t necessary in Zsh. Parameters don’t split or glob by default.
• $array actually expands to every element in an array.

Compare this between Bash and Zsh:

a=('/* hello */' 'world!' '  ')
printf '"%s" ' $a

ZDOTDIR="${${(%):-%x}:P:h}"