Unix-Text-Processing
OpenVi
Our great sponsors
| Unix-Text-Processing | OpenVi | |
|---|---|---|
| 8 | 8 | |
| 202 | 149 | |
| - | - | |
| 0.0 | 7.5 | |
| 8 months ago | 22 days ago | |
| Roff | 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.
Unix-Text-Processing
- Unix for people with 0 background in programming?
- Recreated sources for the book “UNIX Text Processing,” published in 1987
-
Hacker News top posts: Feb 19, 2022
Recreated sources for the book “UNIX Text Processing,” published in 1987\ (2 comments)
- Recreated sources for the book “Unix Text Processing,” published in 1987
-
Can some body help me with tables?
I tend to refer myself mainly to Unix Text Processing which is freely available here and has been revived by the groff community on github.
-
Complete Beginner
For fun, I just checked out the source from github (https://github.com/larrykollar/Unix-Text-Processing), installed a newer version of groff (OSX uses a version that doesn't build PDF files), edited the Makefile in the src directory to point at the new groff utility, and typed make. After 18 seconds on a mid-2011 iMac, I'd build the book (images and all) by hand.
- Best preprocessor for beginners?
-
Sample groff source for thesis paper
Here is a source code to the Unix Text Processing book: https://github.com/larrykollar/Unix-Text-Processing
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)
What are some alternatives?
pyGroff - laTEX is awesome but we are lazy -> groff with markdown syntax and inline code execution
nvi2 - A multibyte fork of the nvi editor for BSD