kakoune VS zee

Helix's modal editing is based on Kakoune's modal editing which is like an evolution to Vim's modal editing. You can think of it as being always in selection (visual) mode. https://github.com/mawww/kakoune?tab=readme-ov-file#selectio...

And while it doesn’t use the sam language precisely, I think in the broader “postfix Vi with visual feedback” category Kakoune[1] also warrants mentioning. The command language, in my experience, feels much more logical than that of Vis coming from a blank slate (things might be different if you come from Vim, but even when I used Vim regularly I never used the editing language that much exactly because I could never remember the damn thing).

And having mentioned Kakoune it’d probably be unfair to then not mention Helix[2]. It has a very similar editing language, but it’s a fairly anti-Unix everything-bolted-in affair on the inside (“everything works out of the box” being the advertising take) compared to Kakoune’s Acme-inspired no-scripting scripting (there’s an ex-style command to exec a user program that can then drive the editor over stdio RPC, a set of hooks, and that’s it). So if you’ve come for the Plan 9 feels, I don’t expect Helix to be that appealing. It’s still a good editor, nevertheless.

[1] https://kakoune.org/

[2] https://helix-editor.com/

> I wonder if the author has ever heard of vis[0]

Yes.

https://github.com/martanne/vis/wiki/Differences-from-Kakoun...

https://github.com/mawww/kakoune/wiki#onboarding

> which imho fulfills far better each one of those premises

Not very motivated for such a harsh critic..

I've been using Vim for years, but if there was one thing I could change, it would be the verb-noun order. The Kakoune[1] editor behaves mostly like Vim, but where Vim has `dw` as "delete word", Kakoune has it backwards: `wd`.

It might sound minor, but by placing the range first, Kakoune can give a preview of what will be changed. The longer or more complicated the command, the more this feature shines.

Strictly better as far as I know. A shame my muscle memory, and all default installations, are still stuck with Vim.

[1] https://kakoune.org/

Helix is a postmodern text editor built in Rust built for the terminal. It is inspired by Kakoune, another Rust based text editor. Helix has got multiple selections, built-in Tree-sitter integration, powerful code manipulation and Language server support.

Sorry if this is a noob question. So suddenly i had this question came to my mind about the helix editor and neovim. Can we write a neovim successor from using rust. i know that helix is inspired by Kakoune Just like that what if we could make a neovim successor using rust. currently helix can't be configured and modified like neovim. if there is a hope to make and vim like editor using rust with much better customization and better plugin support. if there to make an open-source project would you guys be interested in?

That's exactly the model used by the [Kakoune editor](https://kakoune.org/). It definitely feels more intuitive to me, but I personally didn't stick with it due to vim's ubiquity.

you probably forgot to init the git submodules: https://github.com/mcobzarenco/zee#building-from-source

That’s a different editor

One more for the list - I started https://github.com/mcobzarenco/zee last year after trying to contribute to xi-editor, but it was discontinued and I have been disheartened by the architecture and how it makes simple things unnecessarily hard (search issues for soft inserts for example)

Relatedly, there's an Emacs-like editor written in Rust called Zee: https://github.com/mcobzarenco/zee

I've become used to using Micro (written in Go) for everything: https://micro-editor.github.io/

So I haven't really used Amp or Zee much, but I do have both installed on my system just in case I get bored of Micro ;-)