Relevant except below, bolded is the key point.

-v prints non-printing characters in a visible representation. Making strange characters visible is a genuinely new function, for which no existing program is suitable. (sed -n l, the closest standard possibility, aborts when given very long input lines, which are more likely to occur in files containing non-printing characters.) So isn’t it appropriate to add the -v option to cat to make strange characters visible when a file is printed?

The answer is “No.” Such a modification confuses what cat’s job is  concatenating files  with what it happens to do in a common special case  showing a file on the terminal. A UNIX program should do one thing well, and leave unrelated tasks to other programs. cat’s job is to collect the data in files. Programs that collect data shouldn’t change the data; cat therefore shouldn’t transform its input.

I know that “Vanity Addresses” are a common thing for onion sites, and there are tools which generate tons of keys looking for prefixes. I haven’t seen such a tool for ssh host keys though.

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.

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

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

It varies. Reddit is/was the primary forum for a number of projects, and as each sub is community moderated, could be quite rich, even if the whole is “generally full of garbage”.

I did about once a year until 2018 when I settled on Arch.

But now I’ve got a server on NixOS and loving it, so I might be switching my laptop soon.

Excuse me, OCI container, we’re a runtime-agnostic family here.

That it does, thank you! The highlighted +X indicator is appreciated as well.

I’m a fan of this; it’s how Slide handled it.

I also prefer Slide’s method of collapsing comments; it only collapses the child comments, not the one you pressed on. (although it also has an option to collapse it too)

Most Reddit apps I used worked like this by default. It’s not my preference either (I liked Slide because I could swap the tap and long-press actions) but I’m not complaining.