The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Anders Damsgaard <anders@adamsgaard.dk>
To: Clem Cole <clemc@ccc.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Remember the ed thread?
Date: Mon, 29 Mar 2021 17:42:00 +0200	[thread overview]
Message-ID: <YGH1SFEaqf+YagDS@asa.adamsgaard.dk> (raw)
In-Reply-To: <CAC20D2MmaPP-VOJj-7DGEi+CkUMFyUcfoJqVGgwicdYhCwD0Kw@mail.gmail.com>

* Clem Cole <clemc@ccc.com> [2021-03-29 11:37:57 -0400]:

>Anders -- good for you.
>
>That said, as one of those 'grey beards,' can I recommend that you stop,
>and go to a technical library or bookstore and find yourself a copy of Rob
>and Brian's wonderful book: "*The Unix Programming Environment*" (*a.k.a*
>"UPE" or ISBN 0-13-937699-2)  *then do the exercises*.  That book is still
>relevant today - a little secret, I give a copy of it and "*Advanced
>Programming in the Unix Environment*" (*a.k.a.* "APUE") to all my new
>engineers - even though they are all using 'Linux' for their work.  To
>those that object at first, I remind them, Linux is just the current and
>most popular implementation of the ideas from Ken, Dennis, Doug, and
>friends and I'm sure they will learn something from the time invested[1].
>
>FWIW: Besides learning ed (which will help you unlock some of the mysteries
>of other UNIX tools like grep and sed), take a shot at looking at the
>introduction to nroff/troff (as has been discussed here - not to restart a
>war).  Learning to use a 'document compiler' like the troff family is never
>a bad investment.
>
>Have fun,
>Clem
>
>
>1.]  BTW I have yet had a young engineer that actually did try the
>exercises not come back and say something like "Wow, I never knew ...."   I
>don't gloat, but I smile inside, know that I just made them a more
>effective for our team.  If they ask, I point out I had been using UNIX and
>hacking on the kernel most every day for at least 10 years when it first
>appeared in the early 80's (84/85 I think), and I learned a few tricks when
>I read it.

I appreciate the kind advice Clem!  I'm dipping my toes into heirloom
doctools these days, and am delightened by the simplicity, modularity,
and speed compared to latex.  However, much to learn still so thanks
for the nudge.

Anders

  reply	other threads:[~2021-03-29 15:42 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-29 14:34 Larry McVoy
2021-03-29 15:09 ` Anders Damsgaard
2021-03-29 15:26   ` Brantley Coile
2021-03-29 15:36     ` Mark van Atten
2021-03-29 15:43       ` Brantley Coile
2021-03-29 15:52         ` Mark van Atten
2021-03-29 15:45     ` Andy Kosela
2021-03-29 15:51       ` Clem Cole
2021-03-29 17:22       ` arnold
     [not found]         ` <CALMnNGgWrFRjXk5N4PgTj0_Yw3W5nCR2=CYSASM6dnqTooy8Dw@mail.gmail.com>
2021-03-30  8:53           ` arnold
2021-03-29 15:37   ` Clem Cole
2021-03-29 15:42     ` Anders Damsgaard [this message]
2021-03-29 15:49     ` Larry McVoy
2021-03-29 16:01     ` Andy Kosela
2021-03-29 18:12     ` Tom Ivar Helbekkmo via TUHS
2021-03-29 16:20 ` Steve Nickolas
2021-03-29 19:50 ` Rob Pike
2021-03-29 20:50   ` Michael Usher via TUHS
2021-03-29 20:55     ` Larry McVoy
2021-03-29 21:10       ` Erik E. Fair
2021-03-29 21:14         ` Larry McVoy
2021-03-29 21:53         ` Clem Cole
2021-03-29 22:29           ` John P. Linderman
2021-03-30  4:30             ` Rob Pike
2021-03-30  7:37             ` Harald Arnesen
2021-03-30 15:00         ` Kenneth Goodwin
2021-03-29 15:58 Norman Wilson
2021-03-30  0:11 ` John Cowan
2021-03-29 23:21 M Douglas McIlroy
2021-03-30  3:39 ` Rich Morin
     [not found] <CAKH6PiXmR6Jv0bkyOtHuk1ZLV64aeW7bnQkUnzV9-G_JaUVDAA@mail.gmail.com>
2021-03-30 23:38 ` John Cowan
2021-03-31  2:34   ` Bakul Shah
2021-03-31  0:54 Norman Wilson
2021-03-31  1:29 ` 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=YGH1SFEaqf+YagDS@asa.adamsgaard.dk \
    --to=anders@adamsgaard.dk \
    --cc=clemc@ccc.com \
    --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).