Yeah, theres a lot of old old laptops which make no sense to run. But there’s a growing crop of more recent used devices that are only being sold off because they don’t support Windows 11, and the power efficiency story changes there. The OOP mentions “8.1 lappies”; my main laptop has a 15W 8th gen which is only in the last year starting to feel less appropriate for desktop use. (And honestly, a RAM and storage bump will probably get me another couple years.)

For environmental concerns, youve got to tax new devices with manufacturing costs as well.

100% agree about VMs though.

Not as cursed as

print("eovdedn"[n%2::2]) 

I don’t fit into any of those categories.

Its obtuse, old, and doesn’t have a lot of functionality of modern code editors

Obtuse? Yeah. The keyboard focus means natural discoverability is low. But I immediately preferred modal editing once I learned it.

Old? Eh, most people use Neovim nowadays and write plugins in lua. Even in OG Vim, Vim9script broke compatibility for a better dev experience.

Functionality? Out of the box, it is just a text editor. But only VSCode might have a more active plugin ecosystem. ALE has been a thing for ages if it’s LSP support you’re looking for.

It’s not better, it’s not worse, I’m not in any way superior for using it, but I love it for a reason.

Same camp as wtype, you have to bind something to exec it.

autokey

I accomplish the same thing with compose sequences, and by binding a keyboard shortcut in my desktop to call a script with wtype. It’s not a cross-compositor solution though, as you’d have to manually setup binds in each of them.

I don’t see much hope for this one-to-one unfortunately.

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 think each of 3.8 through 3.11 were substantial, just in different ways.

The "$@" doesn’t do that you think it does in an alias. It gets expanded on alias creation.

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.