Basically the Matrix Spec Change Proposal system, I like it. Opens the floor to more players, gives tool authors a list of protocols they could choose to build on, and hopefully compositors will choose to adopt or adapt one of these protocols before writing their own.

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.

I put newlines in my filenames to break both CLI tools and Windows filesystems

Taking courses which involve subjects that you will likely never encounter in the workforce is a thing in every discipline. Most engineers don’t need to manually solve differential equations in their day jobs, they just need to know that they exist and will often require numerical solutions.

Getting your hands dirty with the content provides a better understanding when dealing with higher level concepts.

zsh-syntax-highlighting

There’s also a fork called fast-syntax-highlighting, I use it.

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.

Optional crash reporting was merged. Most of the backlash in the PR is about the significant dependencies (Google’s BreakPad) which were pulled in with it.

However, by default Audacity isn’t built with it, you need to specify a CMake with the URL to send data to. No distros that I know of enable reporting.

Judging purely on the dependencies I see in pacman, nsxiv depends on imlib2, which pulls in a lot of libraries, while imv links to a subset of those libraries directly.

CSS is turing conplete.

What about adding the flags last?

rm deletethisrepo -rf

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

It’s probably the biggest deal for games running in xwayland

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

How is it compared to wofi?

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