string split/collect and similar can't work unless its a builtin. The set foo ( ...... | string ... ) pattern couldn't work if string was an external binary.
Zsh is still king in my book. Fish and Bash don't have the language features, and Zsh completion with menu groups is a premier experience. Fish's completion from manpages is very good, but there's also a standard zsh function to complete from --help output.
If I were to switch shells, it would have to be to nushell.
I've always considered it to be such that the whole thing is simultaneously a joke and true (haha jk, unless?), or maybe just hyperbole. But I've avoided using it myself because clearly it gets misinterpreted way too frequently
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.
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.
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.
-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've got optimizer tendencies, but we've also got another member who is 100% "What would my character do in this high stress situation with the knowledge they have" and I've found myself leaning that way during combat more and more.
I will still scrutinize everything outside of combat though, and I'm thankful for the IRL time pressure to get me out of that.
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.
Single quotes don't allow any escaping in shell, you need
'I don'\''t know what you mean, I'\''ve never encountered any annoyances'Or, in Zsh with
setopt rcquotes:'I don''t know what you mean, I''ve never encountered any annoyances'