(r10) EditorVi < MecrispCube

Tags: view all tags
%DASHBOARD{ section="dashboard_start" }%
%DASHBOARD{ section="banner"
 image="%PUBURLPATH%/MecrispCube/EditorVi/Mecrisp-Cube-vi-header2.jpg"
 title="vi Editor"
 titlestyle="color:#F00000;"
}%
%DASHBOARD{ section="box_start" title="Intro" width="485" height="250"}%
---+ Intro
I was looking for a tiny editor which can be easily adapted and embedded into a (Forth) system. The [[https://en.wikipedia.org/wiki/Editor_war][vi EMACS war]] is over but others have won. However for me vi is better suited for restricted (embedded) systems. I have not used [[https://en.wikipedia.org/wiki/Vi][vi]] for a very long time, but to see a screen full with ~ at the beginning of the lines makes me feel like coming home. I never thought I would ever take the book _Learning the vi Editor_, by Linda Lamb, 5th edition 1990 off the bookshelf again for reading. I kept the book only for sentimental reasons.

My editor history:
   * CP/M Turbo Pascal Editor (Wordstar) OKI if800, Z80 Assembler, Pascal, 1984
   * UNIX Rand Editor, Perkin Elmer, 1985
   * VMS EDT !MicroVAX, Pascal, Oracle DB, 1987
   * vi ([[https://en.wikipedia.org/wiki/MKS_Toolkit][MKS Toolkit]]) IBM PC DOS cross-assembler for NEC's 75X 4-bit MCUs, Coherent OS, Linux, 1988
   * UNIX EMACS as system administrator for DEC Tru64 UNIX, SUN Solaris, and Linux servers, 1996
   * IDE (Eclipse, !NetBeans, EWARM), 2010 


%DASHBOARD{ section="box_end" }%
%DASHBOARD{ section="box_start" title="Contents" width="460" height="250"}%
%TOC%
%DASHBOARD{ section="box_end" }%
%DASHBOARD{ section="box_start"  width="992" height="250" }%
---+ Features
This vi has its origin in !BusyBox tiny vi. But there are some differences:
   * The program is resident. The text buffer and other buffers too. You can leave the program without saving, do some work on the command line and go back to vi and continue the edit task. 
   * The text buffer is restricted to 40 !KiB. Large files have to be split up.
   * 8-bit characters are allowed e.g. UTF8
   * Mecrisp Forth uses DOS/Windows style line endings carriage return and line feed ("\r\n"). Unix (and vi) uses just line feed ("\n"). https://vim.fandom.com/wiki/File_format dos2unix unix2dos
   * The command <b>v</b> evaluates a line.

Don't forget: you can't use any special keys (e.g. cursor movement keys) in the insert/replace mode. 

%DASHBOARD{ section="box_end" }%
%DASHBOARD{ section="box_start"  width="992" height="400" }%
---+ Documentation, Manual
There are plenty of documents about vi:
   * Busybox vi tutorial  https://k.japko.eu/busybox-vi-tutorial.html
   * Learning the vi Editor/BusyBox vi https://en.wikibooks.org/wiki/Learning_the_vi_Editor/BusyBox_vi
   * Unix/Linux - The vi Editor Tutorial https://www.tutorialspoint.com/unix/unix-vi-editor.htm
   * vi Editor "Cheat Sheet" http://www.atmos.albany.edu/daes/atmclasses/atm350/vi_cheat_sheet.pdf
   * The Vi Lovers Home Page ... this makes a great starting point. https://thomer.com/vi/vi.html
   * [[https://doc.lagout.org/operating%20system%20/linux/Learning%20the%20vi%20and%20Vim%20Editors%2C%207e.pdf][Learning the vi Editor, by Linda Lamb]]

---++ !BusyBox and !ToyBox
   * https://git.busybox.net/busybox/plain/editors/vi.c
   * [[https://en.wikipedia.org/wiki/Toybox][Toybox]] 
   * https://github.com/landley/toybox/blob/master/toys/pending/vi.c

%DASHBOARD{ section="box_end" }%
%DASHBOARD{ section="box_start"  width="992" height="300" }%
---+ Usage

%DASHBOARD{ section="box_end" }%

%DASHBOARD{ section="dashboard_end" }%


-- %USERSIG{PeterSchmid - 2020-08-29}%

---++ Comments

%COMMENT%
Attachments
Topic attachments
I	Attachment	History	Action	Size	Date	Who	Comment
jpg	Mecrisp-Cube-vi-header.jpg	r1	manage	69.8 K	2020-09-23 - 18:20	PeterSchmid
jpg	Mecrisp-Cube-vi-header2.jpg	r1	manage	75.0 K	2020-09-23 - 18:27	PeterSchmid
Topic revision: r10 - 2020-09-23 - PeterSchmid