KE-complex_modifications VS fzf

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

In addition, I think bash's `operate-and-get-next` can be very helpful. When you go back through your shell history, you can hit Ctrl+o instead of enter and it will execute the command then put the next one in your history on the command line, and keep track of where you are in your history. This way, you can rerun a bunch of commands by going to the first one and Ctrl+o till you are done. And you can edit those commands and hit Ctrl+o and still go to the next previously run command.

Note: fzf's history search feature breaks this. https://github.com/junegunn/fzf/issues/2399

fzf : https://github.com/junegunn/fzf

Those are the most used aliases in my gitconfig.

"git fza" shows a list of modified/new files in an fzf window, and you can select each file with tab plus arrow keys. When you hit enter, those files are fed into "git add". Needs fzf: https://github.com/junegunn/fzf

"git gone" removes local branches that don't exist on the remote.

"git root" prints out the root of the repo. You can alias it to "cd $(git root)", and zip back to the repo root from a deep directory structure. This one is less useful now for me since I started using zoxide to jump around. https://github.com/ajeetdsouza/zoxide

> my history is so noisy I had to find another way

The fzf search syntax can help, if you become familiar with it. It is also supported in atuin [2].

[1]: https://github.com/junegunn/fzf#search-syntax

[2]: https://docs.atuin.sh/configuration/config/#fuzzy-search-syn...

You call it with `n` and get an interactive fuzzy search for your directories. If you do `n ` instead, it’ll start the find with `` already filled in (and if there’s only one match, jump to it directly). The `ls` is optional but I find that I like having the contents visible as soon as I change a directory.

I’m also including iCloud Drive but excluding the Library directory as that is too noisy. I have a separate `nl` function which searches just inside `~/Library` for when I need it, as well as other specialised `n` functions that search inside specific places that I need a lot.

¹ https://github.com/sharkdp/fd

² https://github.com/junegunn/fzf

View on GitHub

I do find the history pager stuff interesting, but ultimately not of tremendous use for me. I rebound all my history search stuff to use fzf[1] (via a fish plugin for such[2]), and so haven't been aware of the issues

[1] https://github.com/junegunn/fzf

[2] https://github.com/PatrickF1/fzf.fish

You can also use fzf with ripgrep to great effect:

[1]: https://github.com/junegunn/fzf/blob/master/ADVANCED.md#usin...