extrakto VS emacs-which-key

For me personally tmux giver minor improvements (some of them are done by some terminals, some are not), e.g.:

* Text selection using variuos shortcuts (usually I use it only for URL):

https://github.com/tmux-plugins/tmux-copycat

* FZF autocompletion from output, e.g. in case I want to diff some file I see changed in `git status`:

https://github.com/laktak/extrakto

For me, tmux is the terminal/workspace manager, nvim is the editor. If I want to work on a different repo/workspace, I open a new tmux window and open a new nvim in that window. If I need to do stuff on the terminal, opening a new tmux pane feels more natural than opening a new nvim split with a terminal. Also this tmux plugin is great: https://github.com/laktak/extrakto

extrakto - let's you do a fuzzy search across all the words/lines/extracted objects/etc in your pane or window and put it in current command

The extrakto plugin https://github.com/laktak/extrakto

A tmux plugin that I use all the time is extrakto: https://github.com/laktak/extrakto

My favorite is extracto that helps to extract text segments on display so that you don't have to use mouse

I'm using extrakto[0] for it, so far it works nice.

[0]: https://github.com/laktak/extrakto

Only glanced at it but didn't see it mention 'V' which selects rows rather than characters. Which can be quite useful.

There are also tmux plugins to make some operations smoother.

https://github.com/fcsonline/tmux-thumbs

Like keyboard driven browsers uses hints, so file paths, git SHAs etc. are highlighted using a small hint and if you press it it is copied.

https://github.com/laktak/extrakto

Fuzzy search in current pane to insert/copy things of interest.

I think which-key already solves exactly that: https://github.com/justbur/emacs-which-key

As for the "complicated keybindings general" -- I assume because remembering things like C-x C-s is hard because of the shifted keystrokes? I get that, and there is in fact a solution for less used keybindings which I love, called 'which-key' https://github.com/justbur/emacs-which-key

I would recommend installing the which-key package, which is a fantastic discoverability aid. If you ever want an example config to get some inspiration, I have one here: Emacs Bedrock

Make sure you have which-key installed and turned on. When using a keybinding that has a prefix (like C-x or C-c), it displays all the keybindings that start with that prefix.

which-key for the shortcut menus

there are some packages to help with the keybings, which-key shows a list of keybind and its command and (guru-mode)[https://github.com/bbatsov/guru-mode] enforces to use the "best" keybind, for exemple, it forces you to use C-n to move the cursor, blocking you to use the down key, and if you press the down key, it show a text in minibuffer to the best keybind.

"can't find the command associated with C-x" this will help https://github.com/justbur/emacs-which-key

If you haven't already, definitely check out the package which-key.

> even though I'm a terminal user ... I really like the discoverability of GUIs, and that's where a good GUI is unbeatable by CLI.

CLI has poor discoverability? Sure; but even on the terminal, discoverability can still be good:

A couple of nice examples of discoverability in keyboard-focused programs:

- emacs' which-key[0]; there's a vim port[1] too. This shows you (some) of the available keybindings for the next input, and a short label. So you don't have to remember what `SPC h p ...` or all the options under `SPC f...`.. but it still helps to recall that `SPC h` is for 'help' related commands, `SPC f` for file related commands.

- emacs' magit[2][3]. Magit is so good at discoverability, that I'd rate it as the best tool for using git with. I've learned more about git from using it.

[0] https://github.com/justbur/emacs-which-key

[1] https://github.com/liuchengxu/vim-which-key

[2] https://magit.vc/

[3] https://emacsair.me/2017/09/01/magit-walk-through/

Am I right in thinking this is quite similar to which-key?