nextvi
vis
| nextvi | vis | |
|---|---|---|
| 5 | 56 | |
| 124 | 4,171 | |
| - | - | |
| 8.9 | 8.2 | |
| 5 days ago | 2 days ago | |
| C | 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.
nextvi
-
failed local build of `nextvi`
nextvi is a cool minimal editor for people like me who just need a small vi/vim like editor to edit dotfiles and the like.
- NextVI - The Suckless Editor
- [PROJECT] Nextvi Editor
-
Will there be a suckless text editor?
You can have a look at neatvi. I don't use it directly, but this fork. Sometimes I have the impression that I need some missing features, but I'm really happy with it. For example I was forced to create a snippet system and I prefer it over the existing ones.
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
What are some alternatives?
micro-editor - A modern and intuitive terminal-based text editor
kakoune - mawww's experiment for a better code editor
OpenVi - OpenVi: Portable OpenBSD vi for UNIX systems
nvi2 - A multibyte fork of the nvi editor for BSD
vim-visual-multi - Multiple cursors plugin for vim/neovim
VIM-Awesome-Cheatsheet - Cheatsheet for Vim
mle - flexible terminal-based text editor (C)
warpd - A modal keyboard-driven virtual pointer
nvim-select-multi-line - Neovim plugin. select multiple lines that are not adjacent.
bvi-lf - bvi-lf: bvi editor for binary files (hex editor) with large-file support [personal fork]
neovim - Vim-fork focused on extensibility and usability