The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: imp@bsdimp.com (Warner Losh)
Subject: [TUHS] Good ol' ed (Was *ROFF)
Date: Tue, 15 May 2018 09:12:00 -0600	[thread overview]
Message-ID: <CANCZdfpzyP-ntUW-FgZ26FpdN_Yp3C5QoMF8Be0TOT1-_B6B7w@mail.gmail.com> (raw)
In-Reply-To: <F6D4D841-93B0-4D4A-B2CC-7FB9D2FC95E4@ccc.com>

Lord knows I learned Unix by watching my peers type it...

In the long run that was both good and bad, though, since now all I get to
see people type are shell scripts which range from brilliant to rubbish...
The only way to know where on that spectrum things are is to read a bunch
of them... and to get burned a few times stealing the techniques that are
best described, in hindsight, as "it seemed like a good idea at the time."

Warner

On Tue, May 15, 2018 at 8:47 AM, Clem cole <clemc at ccc.com> wrote:

> Yeah.  We lost that and it was a good thing.  Programming became a
> operation between you and your computer in the privacy of your own office.
>
> Sent from my PDP-7 Running UNIX V0 expect things to be almost but not
> quite.
>
> > On May 15, 2018, at 10:37 AM, Larry McVoy <lm at mcvoy.com> wrote:
> >
> >> On Tue, May 15, 2018 at 08:17:38AM -0600, arnold at skeeve.com wrote:
> >> "Ron Natalie" <ron at ronnatalie.com> 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.
> >>
> >> I did learn vi, after having learned ed first.  I drop down to the ex
> >> command line for major regexp-based surgery too.  I also get the
> amazement
> >> from co-workers who watch me do stuff. :-)  This is particularly true
> >> of the, er, younger coworkers (kids today ... :-) who can't manage
> >> outside an IDE.
> >
> > In fairness to them, I don't know how you learn the good stuff outside
> > of a terminal room.  I learned so much by watching the screen change
> > and going "WTF?  How did you do that?"
> >
> > There is only so much you can stuff into a manual.
> > --
> > ---
> > Larry McVoy                     lm at mcvoy.com
> http://www.mcvoy.com/lm
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180515/2412348b/attachment.html>


  reply	other threads:[~2018-05-15 15:12 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 [this message]
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
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=CANCZdfpzyP-ntUW-FgZ26FpdN_Yp3C5QoMF8Be0TOT1-_B6B7w@mail.gmail.com \
    --to=imp@bsdimp.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 NNTP newsgroup(s).