cape VS evil

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!

evil mode

Since we already have vyper-mode, why not add Evil to the stack?

2 stripe blue belt here! I used to use Vim for everything other than Java development and have now adopted Emacs in the same way. I am using it for Clojure and Common Lisp development along with org mode, irc, rss, git and file management

I started with Evil mode and then moved to Xah fly keys before sticking to the emacs bindings. Having the caps lock key bound to CTRL helped me a lot. I don't know if it makes that much of a difference for Emacs but using the DVORAK layout has helped my fingers

There are other bindings you can try like Meow or God mode but I don't know what the adoption rate is like for them. Emacs gives you the flexibility to set it up as you please. As others have mentioned, there may be other keyboard options that might be more helpful as well

https://github.com/emacs-evil/evil

If you already know Vim, you should probably not use Emacs without Evil:

https://github.com/emacs-evil/evil

It gives you comprehensive Vim bindings so what you need to learn to be comfortable in Emacs is very little. As a bonus, it also keeps your RSI risk unchanged.

Emacs is a text ecosystem. And it's trivial to add these shortcuts. Evil[0] basically rewires everything to be Vim.

[0]: https://github.com/emacs-evil/evil

I would *highly* recommend using vim keybindings if you're just getting into it (Doom or just evil). I switched from vim to emacs and tried to rough it with the default keybindings thinking that otherwise I wasn't /really/ using emacs, but I was wrong! I've been using org-mode/emacs for ~2 years now and I've slowly been migrating everything into it as I find useful tools/modes/etc (and now thanks to u/ilemming I have ~12 more to experiment with 😂)

Despite using Emacs as my main editor, I was extremely familiar with Vim since I also used it frequently, and was able to use it quite well, especially because I also used [evil](https://github.com/emacs-evil/evil) in Emacs since Emacs's native keybindings are uncomfortable to use. I never used Vim as my primary editor though because it was cumbersome to configure. As many people say, Vimscript just feels wrong, so I gave up on trying to customize Vim.

uhm... this maybe? https://github.com/emacs-evil/evil

doom is a set of configuration files (to put it lightly 😅) for emacs, a text editor with really really powerful configuration abilities -- your "config files" are actually code in a full-fledged programming language, so people have done things like built package managers in it, or written full emulators for other text editors

Does it look like this? https://github.com/emacs-evil/evil/issues/1778