KE-complex_modifications VS murex

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

This is how murex works too https://github.com/lmorg/murex/blob/master/config/defaults/p...

I agree. I’ve written about this before but this is what murex (1) does. It reimplements some of coreutils where there are benefits in doing so (eg sed, grep etc -like parsing of lists that are in formats other than flat lines of text. Such as JSON arrays)

Mutex does this by having these utilities named slightly different to their POSIX counterparts. So you can use all of the existing CLI tools completely but additionally have a bunch of new stuff too.

Far too many alt shells these days try to replace coreutils and that just creates friction in my opinion.

1. https://murex.rocks

This is exactly what Murex shell does. It has lots of builtin tools for querying structured data (of varying formats) but also supports POSIX pipes for using existing tools like `jq` et al seamlessly too.

https://murex.rocks

Stable is a problem because a lot of these shells don’t offer any guarantees for breaking changes.

My own shell, https://github.com/lmorg/murex is committed to backwards compatibility but even here, there are occasional changes made that might break backwards compatibility. Though I do push back on such changes as much as possible, to the extent that most of my scripts from 5 years ago still run unmodified.

This is similar to how my shell works. It still just passes bytes around but additionally passes information about how those bytes could be interpreted. A schema if you will. So it works as cleanly with POSIX / GNU / et al tools as it does with fancy JSON, YAML, CSV and other document formats.

It basically sits somewhere between Powershell and Bash: typed pipelines like Powershell but without sacrificing familiarity with all the CLI commands you already use day in and day out.

https://github.com/lmorg/murex

As an aside, I’m about to drop a massive update in the next few days that will make the shell even more intuitive to use.