Revision 172021-12-28 - PeterSchmid

Line: 1 to 1

META TOPICPARENT	name="WebHome"

%DASHBOARD{ section="banner"

Line: 52 to 52

Added:

>
>

My sources on GitHub

.

Usage

Revision 162021-01-28 - PeterSchmid

Line: 1 to 1

META TOPICPARENT	name="WebHome"

%DASHBOARD{ section="banner"

Line: 83 to 83

--

Peter Schmid - 2020-08-29

Changed:

<
<

Comments

<--/commentPlugin-->

>
>

This work by Peter Schmid is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.

META FILEATTACHMENT	attachment="Mecrisp-Cube-vi-header.jpg" attr="" comment="" date="1600885241" name="Mecrisp-Cube-vi-header.jpg" path="Mecrisp-Cube-vi-header.jpg" size="71525" user="PeterSchmid" version="1"
META FILEATTACHMENT	attachment="Mecrisp-Cube-vi-header2.jpg" attr="" comment="" date="1600885633" name="Mecrisp-Cube-vi-header2.jpg" path="Mecrisp-Cube-vi-header2.jpg" size="76801" user="PeterSchmid" version="1"

Revision 152020-10-27 - PeterSchmid

Line: 1 to 1

META TOPICPARENT	name="WebHome"

%DASHBOARD{ section="banner"

Line: 10 to 10

Intro

I was looking for a tiny editor which can be easily adapted and embedded into a (Forth) system. The vi EMACS war

is over but others have won. However for me vi is better suited for restricted (embedded) systems. I have not used 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.

Changed:

<
<

My editor history:

>
>

My editor using 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

Revision 142020-10-12 - PeterSchmid

Line: 1 to 1

META TOPICPARENT	name="WebHome"

%DASHBOARD{ section="banner"

Line: 17 to 17

vi (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

Added:

>
>

Atom, VS Code; 2019

Contents

Intro
Features
Documentation, Manual
- BusyBox and ToyBox
Usage
Full-fledged Editors

Changed:

<
<

>
>

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.

Line: 33 to 34

The command v evaluates a line. The command V evaluates a line and inserts the results into the text buffer.
:!<line> evaluates the line and put the result to the status line

Changed:

<
<

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

>
>

Don't forget: you can't use any special keys (e.g. cursor movement keys) in the insert/replace mode. TABs are forbidden too, Mecrisp can't handle TABs.

Line: 65 to 66

vi ( "line<EOL>" -- ) a (Forth) programmer's text editor

Added:

>
>

Full-fledged Editors

Emacs, Vim, Atom, Visual Studio Code.

Visual Studio Code with Forth extension:

Line: 75 to 87

<--/commentPlugin-->

Added:

>
>

META FILEATTACHMENT	attachment="Mecrisp-Cube-vi-header.jpg" attr="" comment="" date="1600885241" name="Mecrisp-Cube-vi-header.jpg" path="Mecrisp-Cube-vi-header.jpg" size="71525" user="PeterSchmid" version="1"
META FILEATTACHMENT	attachment="Mecrisp-Cube-vi-header2.jpg" attr="" comment="" date="1600885633" name="Mecrisp-Cube-vi-header2.jpg" path="Mecrisp-Cube-vi-header2.jpg" size="76801" user="PeterSchmid" version="1"
META FILEATTACHMENT	attachment="vi.c" attr="" comment="" date="1601673508" name="vi.c" path="vi.c" size="113817" user="PeterSchmid" version="1"

Added:

>
>

META FILEATTACHMENT	attachment="VSCode-forth.png" attr="" comment="" date="1602496954" name="VSCode-forth.png" path="VSCode-forth.png" size="17612" user="PeterSchmid" version="1"

Revision 132020-10-09 - PeterSchmid

Line: 1 to 1

META TOPICPARENT	name="WebHome"

%DASHBOARD{ section="banner"

Line: 29 to 29

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

Changed:

<
<

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 v evaluates a line.

>
>

Mecrisp Forth uses DOS/Windows style line endings carriage return and line feed ("\r\n"). Unix (and vi) uses just line feed ("\n"). Files are saved as Unix text files. https://vim.fandom.com/wiki/File_format
The command v evaluates a line. The command V evaluates a line and inserts the results into the text buffer.
:!<line> evaluates the line and put the result to the status line

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

Revision 122020-10-03 - PeterSchmid

Line: 1 to 1

META TOPICPARENT	name="WebHome"

%DASHBOARD{ section="banner"

Line: 53 to 53

Usage

Added:

>
>

vi [-R] [-h] [-c <COLUMNS>] [-r <ROWS>] [FILE..]
   -h show features
   -R Read-only mode. You can still edit the buffer, but will be prevented from overwriting a file.
   -e erase the text buffer
   -c <COLUMNS> screen columns, range 40..128 default 80
   -r <ROWS> screen rows, range 16..30 default 24

Added:

>
>

vi ( "line<EOL>" -- ) a (Forth) programmer's text editor

Revision 112020-10-02 - PeterSchmid

Line: 1 to 1

META TOPICPARENT	name="WebHome"

%DASHBOARD{ section="banner"

Line: 67 to 67

META FILEATTACHMENT	attachment="Mecrisp-Cube-vi-header.jpg" attr="" comment="" date="1600885241" name="Mecrisp-Cube-vi-header.jpg" path="Mecrisp-Cube-vi-header.jpg" size="71525" user="PeterSchmid" version="1"
META FILEATTACHMENT	attachment="Mecrisp-Cube-vi-header2.jpg" attr="" comment="" date="1600885633" name="Mecrisp-Cube-vi-header2.jpg" path="Mecrisp-Cube-vi-header2.jpg" size="76801" user="PeterSchmid" version="1"

Added:

>
>

META FILEATTACHMENT	attachment="vi.c" attr="" comment="" date="1601673508" name="vi.c" path="vi.c" size="113817" user="PeterSchmid" version="1"

Revision 102020-09-23 - PeterSchmid

Line: 1 to 1

META TOPICPARENT	name="WebHome"

%DASHBOARD{ section="banner"

Changed:

<
<

image="/twiki/pub/Cosmac/ForthSTM32WB/nucleo-header.jpg"

>
>

image="/twiki/pub/MecrispCube/EditorVi/Mecrisp-Cube-vi-header2.jpg"

title="vi Editor" titlestyle="color:#F00000;" }%

Line: 64 to 64

Comments

<--/commentPlugin-->

Added:

>
>

META FILEATTACHMENT	attachment="Mecrisp-Cube-vi-header.jpg" attr="" comment="" date="1600885241" name="Mecrisp-Cube-vi-header.jpg" path="Mecrisp-Cube-vi-header.jpg" size="71525" user="PeterSchmid" version="1"
META FILEATTACHMENT	attachment="Mecrisp-Cube-vi-header2.jpg" attr="" comment="" date="1600885633" name="Mecrisp-Cube-vi-header2.jpg" path="Mecrisp-Cube-vi-header2.jpg" size="76801" user="PeterSchmid" version="1"

Revision 92020-09-23 - PeterSchmid

Line: 1 to 1

META TOPICPARENT	name="WebHome"

Changed:

<
<

vi Editor

>
>

vi Editor

Intro

I was looking for a tiny editor which can be easily adapted and embedded into a (Forth) system. The vi EMACS war

is over but others have won. However for me vi is better suited for restricted (embedded) systems. I have not used 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.

Deleted:

<
<

This vi has its origin from 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 v evaluates a line.

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

My editor history:

CP/M Turbo Pascal Editor (Wordstar) OKI if800, Z80 Assembler, Pascal, 1984
UNIX Rand Editor, Perkin Elmer, 1985

Line: 22 to 19

IDE (Eclipse, NetBeans, EWARM), 2010

Added:

>
>

Contents

Intro
Features
Documentation, Manual
- BusyBox and ToyBox
Usage
Full-fledged Editors

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 v evaluates a line.

Changed:

<
<

BusyBox and ToyBox

>
>

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

Added:

>
>

Documentation, Manual

There are plenty of documents about vi:

Busybox vi tutorial https://k.japko.eu/busybox-vi-tutorial.html

Line: 38 to 45

The Vi Lovers Home Page ... this makes a great starting point. https://thomer.com/vi/vi.html
Learning the vi Editor, by Linda Lamb

Added:

>
>

BusyBox and ToyBox

Usage

--

Peter Schmid - 2020-08-29

Revision 82020-09-22 - PeterSchmid

Line: 1 to 1

META TOPICPARENT	name="WebHome"

vi Editor

Changed:

<
<

I was looking for a tiny editor which can be easily adapted and embedded into a (Forth) system. The vi EMACS war

is over but others have won. For me vi is better suited for restricted (embedded) systems. I have not used vi

for a very long time, but to see a screen full with ~ at the beginning of the lines makes me feel comming home.

>
>

I was looking for a tiny editor which can be easily adapted and embedded into a (Forth) system. The vi EMACS war

is over but others have won. However for me vi is better suited for restricted (embedded) systems. I have not used 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.

This vi has its origin from 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.

Added:

>
>

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 v evaluates a line.

Added:

>
>

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

My editor history:

CP/M Turbo Pascal Editor (Wordstar) OKI if800, Z80 Assembler, Pascal, 1984
UNIX Rand Editor, Perkin Elmer, 1985

Line: 33 to 36

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

Added:

>
>

Learning the vi Editor, by Linda Lamb

-- Peter Schmid - 2020-08-29

Revision 72020-09-22 - PeterSchmid

Line: 1 to 1

META TOPICPARENT	name="WebHome"

vi Editor

Changed:

<
<

I have not used vi

for a very long time. The vi EMACS war

is over but others have won. I was looking for a tiny editor which can be easily adapted and embedded into a (Forth) system. But for me vi is better suited for restricted (embedded) systems.

To see a screen full with ~ at the beginning of the lines makes me happy.

>
>

I was looking for a tiny editor which can be easily adapted and embedded into a (Forth) system. The vi EMACS war

is over but others have won. For me vi is better suited for restricted (embedded) systems. I have not used vi

for a very long time, but to see a screen full with ~ at the beginning of the lines makes me feel comming home.

This vi has its origin from 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.

Revision 62020-09-21 - PeterSchmid

Line: 1 to 1

META TOPICPARENT	name="WebHome"

vi Editor

Line: 9 to 9

This vi has its origin from 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.

Changed:

<
<

Mecrisp Forth uses DOS/Windows style line endings carriage return and line feed ("\r\n"). Unix (and vi) uses just line feed ("\n").

>
>

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 v evaluates a line.

My editor history:

Line: 34 to 34

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

Added:

>
>

The Vi Lovers Home Page ... this makes a great starting point. https://thomer.com/vi/vi.html

-- Peter Schmid - 2020-08-29

Revision 52020-09-21 - PeterSchmid

  META TOPICPARENT 
 name="WebHome" 

 vi Editor
- META TOPICPARENT
+ name="WebHome"
-<
<
+I have not used vi for a very long time. The vi EMACS war is over and others have won. I was looking for a tiny editor which can be easy adapted and embed into a (Forth) system.
->
>
+I have not used vi for a very long time. The vi EMACS war is over but others have won. I was looking for a tiny editor which can be easily adapted and embedded into a (Forth) system. But for me vi is better suited for restricted (embedded) systems.
-<
<
+This vi has its origin from BusyBox tiny vi. 
 The program is resident. The buffer 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 buffer is restricted to 40 KiB. Large files have to be split up.
->
>
+To see a screen full with ~ at the beginning of the lines makes me happy.

This vi has its origin from 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.
  Mecrisp Forth uses DOS/Windows style line endings carriage return and line feed ("\r\n"). Unix (and vi) uses just line feed ("\n").
  The command v evaluates a line.
-<
<
+Turbo Pascal IDE (Wordstar), EDT, vi, EMACS, IDE (Eclipse, NetBeans, EWARM)
->
>
+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 (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

Revision 42020-09-20 - PeterSchmid

Line: 1 to 1

META TOPICPARENT	name="WebHome"

vi Editor

Added:

>
>

I have not used vi for a very long time. The vi EMACS war is over and others have won. I was looking for a tiny editor which can be easy adapted and embed into a (Forth) system.

This vi has its origin from BusyBox tiny vi.

The program is resident. The buffer 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 buffer is restricted to 40 KiB. Large files have to be split up.
Mecrisp Forth uses DOS/Windows style line endings carriage return and line feed ("\r\n"). Unix (and vi) uses just line feed ("\n").
The command v evaluates a line.

Turbo Pascal IDE (Wordstar), EDT, vi, EMACS, IDE (Eclipse, NetBeans, EWARM)

Deleted:

<
<

Resident Buffer 40 KiB

Deleted:

<
<

split

Changed:

<
<

BusyBox

>
>

BusyBox and ToyBox

https://git.busybox.net/busybox/plain/editors/vi.c

Deleted:

<
<

ToyBox

Documentation, Manual

Changed:

<
<

>
>

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

Deleted:

<
<

Command v evaluate a line.

--

Peter Schmid - 2020-08-29

Revision 32020-09-17 - PeterSchmid

Line: 1 to 1

META TOPICPARENT	name="WebHome"

vi Editor

Line: 10 to 10

split

BusyBox

Added:

>
>

https://git.busybox.net/busybox/plain/editors/vi.c

ToyBox

Deleted:

<
<

ToyBox

https://git.busybox.net/busybox/plain/editors/vi.c

Documentation, Manual

Revision 22020-09-16 - PeterSchmid

Line: 1 to 1

META TOPICPARENT	name="WebHome"

vi Editor

Added:

>
>

Turbo Pascal IDE (Wordstar), EDT, vi, EMACS, IDE (Eclipse, NetBeans, EWARM)

Resident Buffer 40 KiB

split

BusyBox

Line: 6 to 13

Added:

>
>

ToyBox

https://git.busybox.net/busybox/plain/editors/vi.c

Documentation, Manual

Added:

>
>

https://www.tutorialspoint.com/unix/unix-vi-editor.htm

Command v evaluate a line.

--

Peter Schmid - 2020-08-29

Revision 12020-08-29 - PeterSchmid

Line: 1 to 1

Added:

>
>

META TOPICPARENT	name="WebHome"

vi Editor

BusyBox

ToyBox

https://git.busybox.net/busybox/plain/editors/vi.c

Documentation, Manual

-- Peter Schmid - 2020-08-29

Comments

<--/commentPlugin-->

Difference: EditorVi (1 vs. 17)

Revision 172021-12-28 - PeterSchmid

Usage

Revision 162021-01-28 - PeterSchmid

Comments

Revision 152020-10-27 - PeterSchmid

Intro

Revision 142020-10-12 - PeterSchmid

Features

Full-fledged Editors

Revision 132020-10-09 - PeterSchmid

Revision 122020-10-03 - PeterSchmid

Usage

Revision 112020-10-02 - PeterSchmid

Revision 102020-09-23 - PeterSchmid

Comments

Revision 92020-09-23 - PeterSchmid

vi Editor

Intro

Features

BusyBox and ToyBox

Documentation, Manual

BusyBox and ToyBox

Usage

Revision 82020-09-22 - PeterSchmid

vi Editor

Revision 72020-09-22 - PeterSchmid

vi Editor

Revision 62020-09-21 - PeterSchmid

vi Editor

Revision 52020-09-21 - PeterSchmid

vi Editor

Revision 42020-09-20 - PeterSchmid

vi Editor

BusyBox

BusyBox and ToyBox

ToyBox

Documentation, Manual

Revision 32020-09-17 - PeterSchmid

vi Editor

BusyBox

ToyBox

ToyBox

Documentation, Manual

Revision 22020-09-16 - PeterSchmid

vi Editor

BusyBox

ToyBox

Documentation, Manual

Revision 12020-08-29 - PeterSchmid

vi Editor

BusyBox

ToyBox

Documentation, Manual

Comments