From: arnold@skeeve.com
To: tuhs@minnie.tuhs.org, dbrock@computerhistory.org
Subject: Re: [TUHS] Data structures in Unix editors
Date: Wed, 31 Mar 2021 12:07:57 -0600 [thread overview]
Message-ID: <202103311807.12VI7vpZ022249@freefriends.org> (raw)
In-Reply-To: <D98F28EB-44E6-4359-98B2-6952ABE4F83D@computerhistory.org>
The "Software Tools" books used very simple arrays of characters
to manage the text buffers for their version of 'ed'. Those books
are worth reading in any case. :-)
Arnold
"David C. Brock" <dbrock@computerhistory.org> wrote:
> All of the great discussion on this list about editors has made me curious about the data structures used in the various Unix editors.
>
> I found a great discussion of this for sam in Rob Pike’s publication “The Text Editor sam.”
>
> I’d like to read similar discussions of the data structures for ed, em, ex/vi. If anyone has suggestions of references, they would be very welcome!
>
> Similarly, if there are any pointers to references on some other data structures in editors like TECO, QED and E, I’d welcome them as well.
>
> All the best,
>
> David
> ...........
> David C. Brock
> Director and Curator
> Software History Center
> Computer History Museum
> computerhistory.org/softwarehistory<http://computerhistory.org/softwarehistory>
> Email: dbrock@computerhistory.org
> Twitter: @dcbrock
> Skype: dcbrock
> 1401 N. Shoreline Blvd.
> Mountain View, CA 94943
> (650) 810-1010 main
> (650) 810-1886 direct
> Pronouns: he, him, his
>
>
next prev parent reply other threads:[~2021-03-31 18:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 17:39 David C. Brock
2021-03-31 18:07 ` arnold [this message]
2021-03-31 18:23 ` Richard Salz
2021-03-31 18:20 ` Lars Brinkhoff
2021-03-31 18:49 ` Bakul Shah
2021-04-01 12:56 ` Tony Finch
2021-04-01 14:24 ` Richard Salz
2021-04-01 21:25 ` Dave Horsfall
2021-04-01 21:32 ` John Cowan
2021-04-02 22:40 ` Dave Horsfall
2021-04-02 23:20 ` Adam Thornton
2021-04-03 0:34 ` Jon Forrest
2021-04-05 23:23 ` Mary Ann Horton
2021-04-01 20:12 Noel Chiappa
2021-04-01 20:57 ` John Cowan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202103311807.12VI7vpZ022249@freefriends.org \
--to=arnold@skeeve.com \
--cc=dbrock@computerhistory.org \
--cc=tuhs@minnie.tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).