who wants to collaborate on this:
https://github.com/Zaydiscool777/z-ed
Zayd Mohammed <zaydm@172.24.208.1> writes:
who wants to collaborate on this:
https://github.com/Zaydiscool777/z-ed
Most likely nobody if you don't provide more information.
Even the README.md in the git repo only says "Nothing notable, as this
is unfinished. Any help you give in the project will be helpful.", with
a hand-drawn diagram.
You cross-posted to comp.lang.c and comp.editors, with followups to comp.lang.c. I've cross-posted and directed followups to comp.editors.
This isn't topical in comp.lang.c unless you're talking about the
language.
Of course we want to discuss how to make editors in comp.lang.c.-a Finseth wrote a great book about how to make an Emacs in C, so I've re-added comp.lang.c, and also
added comp.emacs, because who doesn't want to know about completely for-
eign implementation of Emacs from scratch?
So, everyone interested in the subject can just head over to
-a https://www.finseth.com/craft/
grab a copy of the PDF, and /read/ how to make an Emacs, in C.
The designing the edit engine is what fascinates me, regardless of UI. Pity >there are few discussions any more around this topic.
The designing the edit engine is what fascinates me, regardless of
UI. Pity there are few discussions any more around this topic.
UI is influenced by the history of interface hardware: teletype
printers, serial cable terminals, block-mode terminals, PC, PDAs +
stylus, fondle slabs (tablets/smart phones), voice, "mind
control"/direct human interface. These are all interesting too, but
they rely on the edit engine to do the work.
All the best open-source content-creation apps are built around a scriptable/command-line engine with the UI as a separate layer.
On 2026-10-11 17:00, Lawrence DrCOOliveiro wrote:
All the best open-source content-creation apps are built around a
scriptable/command-line engine with the UI as a separate layer.
For me that's a Unix shell (ksh, rc) which provides scripting, plus
AWK, sed, and other similar tools. Unix command line IS the IDE for
me. The `vi` family is built around shell (filter commands, ctags),
etc.
On Sun, 11 Oct 2026 20:50:51 -0400, Anthony Howe wrote:
On 2026-10-11 17:00, Lawrence DrCOOliveiro wrote:
All the best open-source content-creation apps are built around a
scriptable/command-line engine with the UI as a separate layer.
For me that's a Unix shell (ksh, rc) which provides scripting, plus
AWK, sed, and other similar tools. Unix command line IS the IDE for
me. The `vi` family is built around shell (filter commands, ctags),
etc.
Not really good enough any more. The combination of a GUI and a
command line can be more powerful than either alone. GUI gives you copy/paste, which you can apply to command/script snippets --
ironically, the GUI itself doesnrCOt let you apply such operations to
GUI user actions.
[..]--- Synchronet 3.22a-Linux NewsLink 1.2
The designing the edit engine is what fascinates me, regardless of UI. Pity there are few discussions any more around this topic.
UI is influenced by the history of interface hardware: teletype printers, serial cable terminals, block-mode terminals, PC, PDAs + stylus, fondle slabs (tablets/smart phones), voice, "mind control"/direct human interface. These are all interesting too, but they rely on the edit engine to do the work.--- Synchronet 3.22a-Linux NewsLink 1.2
Anthony Howe <achowe@snert.com> writes:
\
The designing the edit engine is what fascinates me, regardless of UI. Pity >> there are few discussions any more around this topic.
I agree. I would love to play with a redisplay engine. let alone read
more about them. I usually just read some old pascal books from the
1990s. I would love to reimplement lotus style menus !
UI is influenced by the history of interface hardware: teletype printers, serial cable terminals, block-mode terminals, PC, PDAs + stylus, fondle slabs
(tablets/smart phones), voice, "mind control"/direct human interface. These are all interesting too, but they rely on the edit engine to do the work.
On 2026-10-12 17:42, steve g wrote:
Anthony Howe <achowe@snert.com> writes:
The designing the edit engine is what fascinates me, regardless of UI. Pity
there are few discussions any more around this topic.
I agree. I would love to play with a redisplay engine. let alone read
more about them. I usually just read some old pascal books from the
1990s. I would love to reimplement lotus style menus !
Redisplay in text, you thinking Curses/NCurses?
Curses was designed to abstract the assorted video terminals of the day (now >everything is an VT100/ANSI derivative) and to optimise the sending of minimal
sequences of escape codes to a **serial terminal** (or terminal emulator) to >update the screen.
There used to be BSD Curses, Solaris Curses, System V Curses, pdcurses, (and >Mortice Kern Systems (MKS) Curses). X/Open (now SUS) created a standard for >Curses that brought together the minor difference into one. NCurses (written in
C++) was starting around the time of POSIX.2, X/Open, and Unicode standards and
hasn't change much since and is stable. SUS has Curses Issue 7 which clarifies
the text.
Terminal Difference algorithms are related to Edit Distance / Longest Common >Subsequence algorithms - think `diff(1)`. There is a paper from Bill Joy on >Curses and some other papers related to terminal Edit Distance/LCS I obtained >when working on MKS Curses (buried on my book shelf).
There are books "Software Tools in PASCAL" by Kernigan & Plauger ISBN >0-201-103342-7 and "A Software Tools Sampler" by Web Miller ISBN 0-13-822305-X
that cover editors. The latter also covers terminal updating for an editor >(Edit Distance/LCS). See also `diff(1)` and my IOCCC 2015 `npdif(1)` also cover
Edit Distance/LCS (I supply several References in the documentation to papers).
Frankly I think terminal updates is a well solved problem - worth learning and
studying since the topic of Edit Distance/LCS relates to other subject areas >like gene sequencing, but not worth a new library IMO.
UI is influenced by the history of interface hardware: teletype printers, serial cable terminals, block-mode terminals, PC, PDAs + stylus, fondle slabs
(tablets/smart phones), voice, "mind control"/direct human interface. These
are all interesting too, but they rely on the edit engine to do the work.
An editor's edit engine covers the storage and its manipulation of the text. >The terminal update display algorithm for an editor would be part of the >UI/hardware interface and as has been mentioned else where GUI for desktop >paradigms.
On 2026-10-12 17:42, steve g wrote:
Anthony Howe <achowe@snert.com> writes:
The designing the edit engine is what fascinates me, regardless of UI. PityI agree. I would love to play with a redisplay engine. let alone read
there are few discussions any more around this topic.
more about them. I usually just read some old pascal books from the
1990s. I would love to reimplement lotus style menus !
Redisplay in text, you thinking Curses/NCurses?
Curses was designed to abstract the assorted video terminals of the day (now everything is an VT100/ANSI derivative) and to optimise the sending of minimal
sequences of escape codes to a **serial terminal** (or terminal emulator) to update the screen.
There used to be BSD Curses, Solaris Curses, System V Curses, pdcurses, (and Mortice Kern Systems (MKS) Curses). X/Open (now SUS) created a standard for Curses that brought together the minor difference into one. NCurses (written in C++) was starting around the time of POSIX.2, X/Open, and Unicode standards
and hasn't change much since and is stable. SUS has Curses Issue 7 which clarifies the text.
Terminal Difference algorithms are related to Edit Distance / Longest Common Subsequence algorithms - think `diff(1)`. There is a paper from Bill Joy on Curses and some other papers related to terminal Edit Distance/LCS I obtained when working on MKS Curses (buried on my book shelf).
There are books "Software Tools in PASCAL" by Kernigan & Plauger ISBN 0-201-103342-7 and "A Software Tools Sampler" by Web Miller ISBN 0-13-822305-X
that cover editors. The latter also covers terminal updating for an editor (Edit Distance/LCS). See also `diff(1)` and my IOCCC 2015 `npdif(1)` also cover Edit Distance/LCS (I supply several References in the documentation to papers).
Frankly I think terminal updates is a well solved problem - worth learning and
studying since the topic of Edit Distance/LCS relates to other subject areas like gene sequencing, but not worth a new library IMO.
An editor's edit engine covers the storage and its manipulation of the text. The terminal update display algorithm for an editor would be part of the UI/hardware interface and as has been mentioned else where GUI for desktop paradigms.
Anthony Howe <achowe@snert.com> writes:
Terminal Difference algorithms are related to Edit Distance / Longest Common >> Subsequence algorithms - think `diff(1)`. There is a paper from Bill Joy on >> Curses and some other papers related to terminal Edit Distance/LCS I obtained
when working on MKS Curses (buried on my book shelf).
yeah, but building the matrix is not easy, especially when the person is currently typing.
There are books "Software Tools in PASCAL" by Kernigan & Plauger ISBN
0-201-103342-7 and "A Software Tools Sampler" by Web Miller ISBN 0-13-822305-X
that cover editors. The latter also covers terminal updating for an editor >> (Edit Distance/LCS). See also `diff(1)` and my IOCCC 2015 `npdif(1)` also >> cover Edit Distance/LCS (I supply several References in the documentation to >> papers).
YES! New Books! Thank you!
Thank you for the descent conversation and my new books that are now
being shipped by amazon, thank you for the recommendations.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 54:34:38 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
3 files (2,684K bytes) |
| Messages: | 285,563 |