nvim-config
vis
nvim-config | vis | |
---|---|---|
1 | 56 | |
2 | 4,181 | |
- | - | |
6.6 | 8.2 | |
about 2 months ago | about 14 hours ago | |
Lua | C | |
- | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nvim-config
-
Why Kakoune
I've used all except Kakoune. For me, Neovim is the one that stuck. Helix is cool, but having no plugins is a deal breaker (for now!) The onboarding experience is much nicer for sure, and Helix's LSP is way easier to set up than Neovim's.
That being said, Neovim, once you get it set up, is great. The biggest hurdle for me was the config, but if you just start from scratch and make a light config (mines about 200-300 lines, with LSP, hints, etc) you can get through it. And you never have to touch it again, since most likely you configured it in a way you like. Well unless you wanna add the occasional plugin. There are also distros of Neovim that contain a fully baked IDE-lite experience, but honestly those have extremely complicated config, and often IME don't feel nice and light.
It's definitely not for everyone. There is that time investment to get started, but it's definitely been worth it for me.
My config: https://github.com/wrapperup/nvim-config
vis
- Vis: A vi-like editor based on Plan 9's structural regular expressions
- Oasis – a small, statically-linked Linux system
-
Why Kakoune
> 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..
-
The Text Editor Sam by Rob Pike
If you want an editor that uses Sam's structural regexes with keyboard-focussed vi-style interaction, you might be interested in https://github.com/martanne/vis
-
Can we write a Neo-vim Successor using rust?
Not Rust, but there's vis which aims to be a Vi(m) inspired editor with Sam's structural regular expressions.
-
Met that guy one the train yesterday
I do not use vim nor a WM nor a Thinkpad, but I do use vis. It's great.
-
Helix: Release 23.03 Highlights
> They either break from Vim's model (kakoune, helix) or follow Vim along with all it's flaws (Neovim, Vis).
I am sincerely curious of what flaws from Vim has Vis inherited, in your opinion.
I have the impression that the design idea of Vis is taking only the modal design of Vi (not Vim), plus the structural regular expressions of Sam, then make it as clean as possible with programmability via Lua plugins.
In fact, the state non-goals [1] seems to clearly distant itself from Vim.
[1]: https://github.com/martanne/vis#non-goals
- Helix: Post-Modern Text Editor
- Mle is a small, flexible, terminal-based text editor written in C