I figured out that #vim introduced #aislop code in their repo and actually #neovim team seems don't have problem to merge this kind of code.

[codedude@floss.social]

I figured out that #vim introduced #aislop code in their repo and actually #neovim team seems don't have problem to merge this kind of code.

For me is unfortunally, but it something that is happening.

I'm not ready to migrate all my way to #code and my way to work, becauase my #neovim setup makes me proud. Long time ago I started to work with vim/neovim so I have them deep in my mind.

Nevetheless I think I should start to learn alternatives, maybe #emacs

[lens_r@mastodon.social]

@codeDude heard of `evil-mode`? DOOM Emacs?

They provide modal editing (like vi) in Emacs

[enfors@mastodon.social]

@codeDude As someone who has used vi/vim and Emacs since 1995, and enjoy using both of them, I would definitely encourage you to switch to #Emacs under these circumstances. It's a different feel compared to #vim but still similar, because they're both text and keyboard based, and very nerdy.

I find that Emacs is an extremely mature product which supports *anything* I want to do with it. It makes me very imatient with other, less capable software.

[benjamineskola@hachyderm.io]

@codeDude I like emacs (as well as vim), but there’s also a fork of vim: evi

evi

evi - EVi, a hard-fork of Vim v9.1.0 (Jan 2024) before AI was used in the project.

Codeberg.org (codeberg.org)

[codedude@floss.social]

@benjamineskola Yeah I had a conversation with the maintainer of this fork.
The problem is that all my setup is addapted to lua and neovim. In all case I'd need a nevi(neoevi) hahaha.

Certantly evi is good propose but I'll wait and watch the develop of the repo and it the same probably give oportunitty to others editors.

Also there is the possibility that neovim team make a desition about regulate the ai shit or create a policy about it.