OpenVi

OpenVi: Portable OpenBSD vi for UNIX systems (by johnsonjh)

OpenVi Alternatives

Similar projects and alternatives to OpenVi

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better OpenVi alternative or higher similarity.

OpenVi reviews and mentions

Posts with mentions or reviews of OpenVi. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-02-19.
  • Portable OpenBSD vi for Unix systems
    1 project | news.ycombinator.com | 26 Aug 2023
  • Genealogy of Vim (2017)
    1 project | news.ycombinator.com | 23 Apr 2023
  • OpenVi: Portable OpenBSD vi for Unix systems
    1 project | /r/hackernews | 19 Feb 2022
    13 projects | news.ycombinator.com | 18 Feb 2022
    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
    6 projects | /r/hackerdigest | 19 Feb 2022
    OpenVi: Portable OpenBSD vi for Unix systems\ (22 comments)
  • A note from our sponsor - WorkOS
    workos.com | 25 Apr 2024
    The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →

Stats

Basic OpenVi repo stats
8
149
7.5
18 days ago

Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com