copilot.el VS helix-vim

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

I tried to re-learn from Vim to Helix but failed. No sure if this is a muscle memory problem or perhaps article is right about cons Kakoune-like approach for me. Even adapting with something https://github.com/LGUG2Z/helix-vim did not work. So if you like Helix it probably a good thing that you did not learn the vim at the time.

Not that they're inherently worse, just different - I'm perfectly happy with vim motions and relearning to type is pretty low on my list of priorities. Luckily there is a compatibility hack, not perfect but it's close enough: https://github.com/LGUG2Z/helix-vim

I want to like Helix, I really, really want to. It's lean, fast, polished, purely console based so it fits my workflows perfectly... but the almost-like-vim-but-not-really key bindings are a deal breaker. I just can't make the switch.

If Helix were completely different in this regard, like Emacs is, I could handle--and I know because I use both vim and Emacs regularly pretty fluently. But Helix is way too close to the vim keybindings to discern it from a memory muscle perspective. I use vim keybindings everywhere else (zsh, all readline-based apps via a setting in ~/.inputrc, VSCode), so getting used to slight differences in just one editor is extremely hard because I can't just drop all other apps.

I recently tried this: https://github.com/LGUG2Z/helix-vim which attempts to provide vim mappings to Helix. It's funny how the description in the page describes my progression almost 100%. And while it makes things slightly better, it's still not accurate enough to make this a non-issue.

https://github.com/LGUG2Z/helix-vim somebody on the internet has you covered

There is this configuration: https://github.com/LGUG2Z/helix-vim

This switches most keybinds to be vi-like.