Gamma, gamma@programming.dev

keyboard first but mouse available

Sway works really well with mod+drag, but the configuration is nearly the same as i3. Plasma’s new tiling features are really good, but unfortunately mousse driven.

I’d check out the COSMIC beta, might be a good middle ground.

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'

Nothings bad about it. I don't think it's strictly better or worse. Just

• I'm used to it
• The comparison in the video was just disingenuous.

I get annoyed by differences with (Ba|Z)sh when I try Fish, but nushell is so much its own thing that it's fun.

Scrubbing through the video, this hurts my soul
bash echo $(echo $STRING | sed 's/World/Bash/')
For variables bash has PE forms:
bash echo ${STRING/World/Bash}
I miss these too much when I try Fish.

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.

100% agree about VMs though.

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.