From: "Lee D. Rothstein" <l1ee057@veritech.com>
To: The Vulgar and Unprofessional Cygwin-Talk List <cygwin-talk@cygwin.com>
Subject: Re: Updated: ed-1.6-1
Date: Thu, 26 Apr 2012 08:39:00 -0000 [thread overview]
Message-ID: <4F990995.1070807@veritech.com> (raw)
In-Reply-To: <0105D5C1E0353146B1B222348B0411A20A6E685C1D@NIHMLBX02.nih.gov>
Long ago (circa 1979), and far away (Ball Labs, CO), I wrote a
text retrieval system in 'ed'. Shortly thereafter, I started
using MicroEmacs.
I later replaced 'ed' in the retrieval system with 'ex' and awk. (I
always disliked 'vi' -- the visual editor-wannabe.)
Before that, circa 1975, I used a programmable forms letter
system, called 'fed' on a pre-BSD (PDP 11-45?, at NASA Ames) that
used 'ed' for a very flexible form letter system, that I used to
get my job at Bell Labs.
Now, I use TextPad. Nice, but all but dead, and only single
platform -- Windows -- and missing some key features.
BTW, 'ed' is not, by far, the worst editor that I ever used.
'edlin' was worse, by far, 'and 'Inted' on the HP 21MX, was the
very worst.
Also, 'learn', a very clever computer learning system for UNIX
(TM -- some damn bunch of ganiff lawyers ;-)) and the shell
(Bourne), by Kernighan, was based, in part, on 'ed'.
'ed' -- long may it wave[r]. ;-)
On 4/23/2012 9:33 PM, Buchbinder, Barry (NIH/NIAID) [E] wrote:
> Christopher Faylor wrote on April 23, 2012 7:17 PM
>> On Mon, Apr 23, 2012 at 06:44:23PM -0400, Buchbinder, Barry
(NIH/NIAID) [E] wrote:
>>> Christopher Faylor wrote on Sunday, April 22, 2012 4:59 PM
>>>> I've made a new version of ed available for installation. This
version
>>>> is a refresh from the currently released FSF version of this package.
My guess is they added a new '--ultra-terse' feedback option. ;-)
Although, fittingly, I'm speechless in trying to describe what
that might mean.
I rejoice! >8-}
>>> They're still updating ed!?!?!
>> I was pretty surprised too. I couldn't believe I'd missed several
revisions.
>> Who in the world still uses ed?
> I was thinking more along the lines of "They are still finding
bugs!?!?!" and
> "They are still adding features!?!?!"
> Can we agree that ed is a better exemplar of software that just won't
go away than B20?
> - Barry
> Disclaimer: Statements made herein are not made on behalf of NIAID.
:wq
Lee
--
-- Lee Rothstein
Disclaimer: Statements made herein, are, best (worst?) case, the
opinions of Lee Rothstein -- if anyone at all. ;-)
next prev parent reply other threads:[~2012-04-26 8:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 22:44 Buchbinder, Barry (NIH/NIAID) [E]
2012-04-23 23:17 ` Christopher Faylor
2012-04-23 23:45 ` Yaakov (Cygwin/X)
2012-04-24 10:26 ` Chris Sutcliffe
2012-04-24 14:36 ` Christopher Faylor
2012-04-24 15:02 ` Corinna Vinschen
2012-04-24 15:46 ` Christopher Faylor
2012-04-25 3:16 ` Warren Young
2012-04-25 3:55 ` Christopher Faylor
2012-04-24 1:34 ` Buchbinder, Barry (NIH/NIAID) [E]
2012-04-24 1:42 ` Christopher Faylor
2012-04-26 8:39 ` Lee D. Rothstein [this message]
2012-04-26 14:41 ` Christopher Faylor
2012-04-26 15:55 ` Buchbinder, Barry (NIH/NIAID) [E]
2012-04-27 2:45 ` Warren Young
2012-06-03 23:53 ` zukkoshopservice
2012-06-03 23:54 ` zukkoshopservice
2012-04-25 13:42 Buchbinder, Barry (NIH/NIAID) [E]
2012-04-25 14:08 ` Christopher Faylor
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=4F990995.1070807@veritech.com \
--to=l1ee057@veritech.com \
--cc=cygwin-talk@cygwin.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).