cape VS emacs-which-key

Wow, interesting that my response is getting down voted. It seems not enough that I give away my work for free. Nevertheless I appreciate support from the community, as other Emacs package developers. The support is actually helpful. To clarify, publishing my configuration would translate into quite a bit of work, requiring separation of private and public bits.

At least for Elisp source block one can use font locking to create a custom Capf. Add cape-elisp-block from my Cape package to completion-at-point-functions. Even if you don't want to use Cape you could just copy it to your config. It is a short function.

You can use cape-history from my Cape package. This is similar to consult-history only utilizing completion-in-region instead of completing-read.

Haven't tried configuring it accordingly, but here's the docs: https://github.com/minad/cape

corfu is blazingly fast. Orderless is as well. What is not always blazingly fast is your completion providing backend. You didn't mention where your slow completions are coming from. An LSP server? Dabbrev? Maybe a remote machine? Have you combined results from various backends (e.g. using cape?). Some completions backends are unavoidably slow, others are just not well optimized.

The most straight forward solution is probably the package company-math. (that's what I use but with corfu and cape)

Some time I'll add a mixin for Cape which would make the completion stuff really nice.

If you're set on using the completion system (M-TAB) for this, you could install Cape and use the cape-abbrev command to complete your abbrevs.

Oh, of course your efforts are valuable. I didn't mean to sound discouraging in any way. The point made by /u/xenodium is good - if you have a special candidate source with special behavior, it makes sense to provide a separate lightweight Capf. In contrast, using Tempel for this purpose doesn't make much use of the actual template functionality. Tempel is only a good fit for Org blocks if you use it already anyway, as I do. There is also value in having reference Capfs around, which will be helpful when developers create their own new completion functions. This was also the intention when I created my Cape package, which comes with many simple Capfs. It is always interesting to see what other Emacs users come up with. I am thankful for such efforts - it is inspiring!

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.

Thanks for confirming, I think it's an issue in which-key itself: https://github.com/justbur/emacs-which-key/pull/166

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?