From: lark@world.std.com (Lar Kaufman)
To: Charles Hallenbeck <2ndsight@taconic.net>, blinux-list@redhat.com
Cc: ;;@world.std.com, shown:@redhat.com@world.std.com,
not@world.std.com, list@world.std.com, recipient@world.std.com,
Blind Linux Discussions <blinux-list@redhat.com>,
Blind Linux Discussions <blinux-list@redhat.com>,
Lar Kaufman <lark@world.std.com>
Subject: Re: where are docs for "ex"
Date: Thu, 17 Dec 1998 14:56:52 -0500 [thread overview]
Message-ID: <199812171956.AA18600@world.std.com> (raw)
True, "ed" is the original unix editor, and has some obscure advantages
in that its command format is used by unix for file parsing. For example,
when you run "diff" on two files, the output is an ed script that would
convert the first one to the second. But nobody does that stuff anymore.
The "ex" editor is an "extended ed" enriched with features that everyone
wanted in the Berkeley Standard Distribution. The ex and vi editors
were, if I recall correctly, both written by Bill Joy, who later founded
Sun. They were developed to meet students' needs, as opposed to the
original ed, which was written by um, Dennis Ritchie? at Bell Labs. A
programmer's tool.
-lar
"This ain't no party, this ain't no disco, this ain't no fooling around. No
time for dancing or lovey-dovey, I ain't got time for that now. I sent a
message through the receiver, hope to get an answer someday. Why stay in
college? Why go to night school? Thought I'd be different this time." -D. Byrne
next reply other threads:[~ UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
Lar Kaufman [this message]
[not found] <367B2DFB.1178@ase.com>
` Jude Dashiell
[not found] <m0zrCuB-0006I3C@vanzandt.mv.com>
` Jude Dashiell
-- strict thread matches above, loose matches on Subject: below --
Lar Kaufman
Lar Kaufman
` Charles Hallenbeck
` Dave Mielke
Lar Kaufman
` Charles Hallenbeck
Charles Hallenbeck
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=199812171956.AA18600@world.std.com \
--to=lark@world.std.com \
--cc=2ndsight@taconic.net \
--cc=blinux-list@redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).