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.

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

If you say “a 10d10”, I know what you mean, but “10d10” is definitely the sum of 10 10-sided dice.

Nope. If you open a nonexistent path and you have permissions to write to that directory, then that file is created.

Move the keyboard to the floor

I grew up with Fahrenheit, but switched my weather app to use Celsius for a while, and I’ve internalized it pretty well. It works fine. The “human experience” angle doesn’t work anyway because that experience is very locale-dependent.

Our group did a two-part Microscope-like after a “season” of 14 sessions to wrap up a ton of loose ends and set up the next season. It was super satisfying to zoom in on only what the players wanted to see and resolve.

Our first session of January is going to be another Microscope session too, we’ve got a giant pointcrawl to backtrack and see the fallout of our action or inaction.

Its incredibly common to be thrown by this. Like many memes, the original incarnations were to be taken at face value, but then a layer of irony got applied, and the ironic/self-deprecating variant became the norm.

*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

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