OpenVi
nextvi
Our great sponsors
| OpenVi | nextvi | |
|---|---|---|
| 8 | 5 | |
| 149 | 122 | |
| - | - | |
| 7.5 | 8.9 | |
| 22 days ago | 12 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.
OpenVi
- Portable OpenBSD vi for Unix systems
- Genealogy of Vim (2017)
-
OpenVi: Portable OpenBSD vi for Unix systems
The behavior of the traditional vi is much different than vim and other clones. Nvi was a actually a re-implementation of the traditional vi for 4BSD (to be clean of AT&T code) and thus was originally intended to be bug-for-bug compatible, but breaking away where the original vi behavior was nonsensical or terrible.
For vim, `set compatible` or `set cp` is close, but still not traditional vi by any means.
A multibyte variant of the tradition vi is maintained - https://github.com/n-t-roff/heirloom-ex-vi/.
Nvi (now on version 1.8x) is also maintained - https://repo.or.cz/nvi.git
Nvi2 is yet another fork of Nvi, https://github.com/lichray/nvi2
Despite the very similar names, all of these editors have a variety of different features, and are structured very differently.
Nvi has a concept of a front-end and a back-end (which uses the BDB database). OpenVi uses the OpenBSD version of Berkeley DB which derives from 1.85. Nvi (1.8x) provides a minimal version of code also derived from that release intended from use with Nvi, and (IIRC) also provides support for using Db3/4/5. Similar situation for Nvi2.
Nvi 1.8 has been structured where a third library layer has been added, which doesn't exist in OpenBSD's vi or OpenVi. There is scripting support (Tcl, Perl, etc.) and GUI code in the other various forks ... all of these support various different options as well.
I should probably make a matrix of these, but you can get an idea by looking at the settable options implemented in each of the variants (as they historically include a comment to document from where the option originated):
OpenVi: https://github.com/johnsonjh/OpenVi/blob/22c2a7022e31d91e09e...
OpenBSD vi: https://github.com/openbsd/src/blob/master/usr.bin/vi/common...
Nvi2: https://github.com/lichray/nvi2/blob/5fcdc13656500a8c5b4c073...
Nvi1: https://repo.or.cz/nvi.git/blob/HEAD:/common/options.c#l52
-
Hacker News top posts: Feb 19, 2022
OpenVi: Portable OpenBSD vi for Unix systems\ (22 comments)
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.
What are some alternatives?
nvi2 - A multibyte fork of the nvi editor for BSD
vis - A vi-like editor based on Plan 9's structural regular expressions
grist-core - Grist is the evolution of spreadsheets.
micro-editor - A modern and intuitive terminal-based text editor
src - Read-only git conversion of OpenBSD's official CVS src repository. Pull requests not accepted - send diffs to the tech@ mailing list.
heirloom-ex-vi - The Traditional Vi (vi with many enhancements from Gunnar Ritter)
VIM-Awesome-Cheatsheet - Cheatsheet for Vim
signify - OpenBSD tool to sign and verify signatures on files. Portable version.
warpd - A modal keyboard-driven virtual pointer
pEmacs - pEmacs - Perfect Emacs
bvi-lf - bvi-lf: bvi editor for binary files (hex editor) with large-file support [personal fork]