Gamma

manually call the others

Yeah, most distros will set up source chains to make things nicer for users.

Yeah, I’d write this as a single update script with options to update vimplugins or update pkg or update all.

I see that you want it to be a function so you can get the chdir as a side effect, but mixing that with updating doesn’t make sense to me.

When in doubt, ~/.zshrc. It’s the right choice 99% of the time. Otherwise, there’s a chance you fuck up scripts you’ve installed which assume no shell options have been changed in non-interactive contexts.

What kind of functions do you write which you share between your scripts? Generally if I’m wanting to reuse a non-trivial function, I extend the functionality of the first script instead.

Select the color which matches the steps before filenames ((non-)login and (non-)interactive), then follow that arrow the rest of the way. There’s more colors in Bash because Bash makes a distinction between remote and local shells.

Another way to look at the same data for Zsh (note: $ZDOTDIR will be used instead of $HOME if it’s defined at any step along the way):

One confusion on the Bash side of the diagram is that you see branching paths into ~/.profile, ~/.bash_profile and ~/.bash_login. Bash will use for ~/.bash_profile, ~/.bash_login, and ~/.profile, in that order, and execute only the first one that exists and is readable.

CSS is turing conplete.

You could still NAT between v6’s though.

I care mostly about shell scripting, so I’m focusing on those bits. Via the HackerNews thread, mostly from a-french-anon:

• readlink and realpath
• find -print0, xargs -0 and read -d
• find -iname
• sed -E
• set -o pipefail
• $' ' strings

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

in the OP

My reply is to a commenter who said they prefer "${HOME}/docs" over both options in the original image ("$HOME/docs" or "$HOME"/docs). Many people prefer to always include braces around the parameter name out of consistency, instead of only when they are required.

My comment explained why my habit is to only include braces when they are necessary.

It’s interesting, the results here are way different than the Code Golf & Coding Challenges Stack Exchange. I would never expect Haskell to be that low. But after looking at code.golf, I realize it’s because I/O on CG&CC is more relaxed. Most Haskell submissions are functions which return the solution.

Sidenote: I like the CG&CC method, it’s semi-competitive, semi-cooperative.

• all languages welcome
• almost all users post “Try it Online”/“Attempt This Online” links
• most users post explanations under their submissions
• often people will post solutions beginning with “port of user1234’s excellent Foolang answer” when there’s a clever shortcut someone finds
• or people will post their own solution with “here’s a solution which doesn’t use user1234’s algorithm”
• or people will add comments to answers with minor improvements

IMO It’s geared towards what is the best part about code golf: teaching people about algorithm design and language design.

This has never stuck with me, and I hadn’t thought about why until now. I have two reasons why I will always write ${x}_$y.z instead of ${x}_${y}.z:

• Syntax highlighting and shellcheck have always caught the cases I need to add braces to prevent $x_ being expanded as ${x_}.
• I write a lot of Zsh. In Zsh, braces are optional in way more cases. "$#array[3]" actually prints the length of the third item in array, rather than (Bash:) the number of positional parameters, then the string 'array[3]'.

This isn’t true. Shellcheck doesn’t insist on braces unless it thinks you need them.

Typically 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"