The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: tytso@mit.edu (Theodore Y. Ts'o)
Subject: [TUHS] Good ol' ed (Was *ROFF)
Date: Tue, 15 May 2018 12:54:25 -0400	[thread overview]
Message-ID: <20180515165425.GB17777@thunk.org> (raw)
In-Reply-To: <01e701d3ec45$e7211580$b5634080$@ronnatalie.com>

On Tue, May 15, 2018 at 08:11:48AM -0400, Ron Natalie wrote:
> I never really learned VI.   I can stumbled through it in ex mode if I have
> to.   If there's no EMACS on the UNIX system I'm using, I use ed.
> You get real good at regular expressions.    Some of my employees were
> pretty amazed at how fast I could make code changes with just ed.

/bin/ed's commands are mostly the same as the line editing tools that
Dec's PDP-8's 4k disk monitor system, PDP-15 backround/foreground
monitor, and the RT-11's editor.  I learned it on my own, from the
manuals only --- and when you are using an teletype, you have a *huge*
amount of incentive to learn all of the tricks you can.

So my choice of editors largely follows Ron; I never really learned
VI, so it's Emacs or ed.  And if you're on a ghastly slow
internet-on-an-airplane connection, being able to use ed is a really
useful skill --- it just gives you flashbacks to using a teletype as
an interface.


       	  	       	     	    - Ted


  parent reply	other threads:[~2018-05-15 16:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-15 12:11 Ron Natalie
2018-05-15 14:17 ` arnold
2018-05-15 14:37   ` Larry McVoy
2018-05-15 14:47     ` Clem cole
2018-05-15 15:12       ` Warner Losh
2018-05-15 15:09     ` arnold
2018-05-15 15:18       ` Larry McVoy
2018-05-15 15:34         ` Jon Steinhart
2018-05-15 16:36           ` Warner Losh
2018-05-15 23:31         ` Dave Horsfall
2018-05-15 16:54 ` Theodore Y. Ts'o [this message]
2018-05-15 20:04 ` Cág

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=20180515165425.GB17777@thunk.org \
    --to=tytso@mit.edu \
    /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).