copilot.el VS cape

Yeah and there's already a well-known (at least I already knew about it) package started in 2022 called "copilot" for Emacs that is actually a client for GitHub Copilot: https://github.com/zerolfx/copilot.el

Given the lack of namespacing in Elisp (or, rather, the informal namespacing conventions by which these two packages collide) it's unfortunate that this package chose the same name.

It's a package to integrate Bigcode/Starcoder into Emacs like https://github.com/zerolfx/copilot.el does with Github Copilot.

It's not fancy with previewable overlays and stuffs as https://github.com/zerolfx/copilot.el and I am not so sure if the performance is optimal, but it gets the bare job done.

Unfortunately, the only way I've managed to get code completion working without having to use the C-c ' buffer is through the unofficial copilot.el. The good news is that it work for any language (including elisp literate configs) but it's a little too aggressive on it's completions.

I'm trying out github copilot with this package: https://github.com/zerolfx/copilot.el, configured like this:

that was enough for this to work from https://github.com/zerolfx/copilot.el

Devs could use the unofficial plugin for Emacs (https://github.com/zerolfx/copilot.el) as a guideline to add support

The whole gif in the repo's README

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!