KE-complex_modifications VS fish-shell

This bad commit message keeps resurfacing on HN front page like beach litter. I would just go with "Remove non-breaking space characters" instead of writing a Russian novel. Also, if you're on macOS just use a Karabiner rule [0] that converts all non-breaking space characters to regular space characters to prevent yourself from accidentally typing it out.

[0] https://ke-complex-modifications.pqrs.org/#nonbreaking_space

you are welcome! Karabiner-Elements complex_modifications rules, for even more inspiration: https://ke-complex-modifications.pqrs.org/ And if you are not familiar with the Hyperkey: https://brettterpstra.com/2017/06/15/a-hyper-key-with-karabiner-elements-full-instructions/

On macOS I use Karabiner-Elements. I remapped right Command to Control and now have two Control and two Meta keys, and can use one hand for modifier keys and the other for letter. For the occasional Command I use the left one. I’ve also extended a bit Emacs complex modifications and I’m quite happy withe the setup. Caveat: I think that due to how I use modifier keys the double keys combinations don’t always work. But have never debugged it deeper.

it would also be helpful is anyone is aware of a modifier rule that exists on https://ke-complex-modifications.pqrs.org/

Rule

More resources on this - https://ke-complex-modifications.pqrs.org/

I was using my friend's Microsoft Surface Ergonomic Keyboard when I was staying at their house for a few days. I really liked the keyboard so I bought one for myself. It's a great keyboard, but the function key behavior is a bit annoying. Pressing the function key just toggles a little light on the key, and doesn't actually send any keypress event. macOS also thinks that this keyboard has a globe key for some reason. So it took me a long time to figure out how to start dictation and come up with this workaround that I posted on StackExchange.

I actually really enjoyed finding a solution for this problem, and I'm really impressed with Karabiner-Elements. I've been reading through the complex rule examples on their documentation site [1], and there's some really cool ideas.

I like the idea of setting up keyboard shortcuts to launch apps [2]. There's also a safeguard for command-q, so you always have to press it twice. (Google Chrome already does this, so you could set up a condition to ignore the rule if Google Chrome is the active application.)

[1] https://ke-complex-modifications.pqrs.org

[2] https://ke-complex-modifications.pqrs.org/#apps_launch_any_l...

[3] https://ke-complex-modifications.pqrs.org/#command_q

Reminds of the note at the bottom of Fish's releases. It's there because the build system cannot determine the current version for some reason. Hopefully that will go away now that they have switched to a different language / build system. The custom tarball is used by Arch Linux at the very least.

https://github.com/fish-shell/fish-shell/releases/tag/3.7.1

https://github.com/fish-shell/fish-shell/issues/7772#issueco...

https://gitlab.archlinux.org/archlinux/packaging/packages/fi...

A recent practical example of the former: the fish shell re-wrote incrementally from C++ to Rust, and is almost finished https://github.com/fish-shell/fish-shell/discussions/10123

An example of the latter: c2rust, which is a work in progress but is very impressive https://github.com/immunant/c2rust

It currently translates into unsafe Rust, but the strategy is to separate the "compile C to unsafe Rust" steps and the "compile unsafe Rust to safe Rust" steps. As I see it, as it makes the overall task simpler, allows for more user freedom, and makes the latter potentially useful even for non-transpiled code. https://immunant.com/blog/2023/03/lifting/

And this discussion from November has an update on the progress: https://github.com/fish-shell/fish-shell/discussions/10123

We're using bash as our terminal shell for now (it is standard in many distros) but it is not the only one out there. If you want to test out zsh, fish or oh-my-zsh, you will see that there are a few differences and the features are usually the main differentiator. Try that, poke around.

They have a variety of reasons to move to rust, as outlined in their original rust discussion[1]. Mostly around finding other contributors, and adding an async/parallel mode they're comfortable with.

[1] https://github.com/fish-shell/fish-shell/pull/9512