The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Andreas Kusalananda Kähäri" <andreas.kahari@abc.se>
To: Steve Nickolas <usotsuki@buric.co>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] manual humour (was tunefs -m 5%)
Date: Wed, 10 Mar 2021 19:37:33 +0100	[thread overview]
Message-ID: <20210310183733.GA14019@box.prefix.duckdns.org> (raw)
In-Reply-To: <alpine.DEB.2.21.2103091850310.15857@sd-119843.dedibox.fr>

On Tue, Mar 09, 2021 at 06:51:56PM -0500, Steve Nickolas wrote:
> On Wed, 10 Mar 2021, Rob Pike wrote:
> 
> > I'm curious when people (other than me) erred and stopped saying that ed
> > was the standard editor.
> > 
> > -rob
> > 
> 
> I actually use that expression in somewhat unorthodox ways. ;)
> 
> Like "CDE is the standard desktop environment like ed is the standard text
> editor." (I still consider both to be true even though about no one uses
> either anymore.)
> 
> -uso.

Hi, I'm "about no one".  I use ed(1) every once in a while, both the
way it was supposed to be used, i.e. interactively, and occasionally
scripted on smaller documents.

I'm soon 50.  Having grown up with computers, and having spent most of
my money as a student buying the next bigger and/or faster PC, I find
that I nowadays enjoy smaller, slower systems and simpler editors more
and more.  Getting distracted by syntax highligting, confused by too
complicated configurations... There is a certain beauty in the editing
language of ed(1).  It's minimalistic and restrictive, and therefore
forces you to think, to remember, and to be creative.

One of my big sorrows is not *having* to deal with ed(1) as a youngster
or student, over slow modem links.  I think I would appreciate Unix even
more now if I had.  I was born one or two decades too late.

ed(1) is still the standard editor though, and so is ex(1) and vi(1), at
least if POSIX is to be believed :-)


-- 
Andreas (Kusalananda) Kähäri
SciLifeLab, NBIS, ICM
Uppsala University, Sweden

.

  parent reply	other threads:[~2021-03-10 18:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-09 16:21 Norman Wilson
2021-03-09 20:11 ` Henry Bent
2021-03-09 20:22   ` Steffen Nurpmeso
2021-03-09 20:36     ` Henry Bent
2021-03-09 22:30       ` Rob Pike
2021-03-09 22:46         ` Larry McVoy
2021-03-09 23:51         ` Steve Nickolas
2021-03-10  0:01           ` Rob Pike
2021-03-10  0:13             ` Anthony Martin
2021-03-10 18:37           ` Andreas Kusalananda Kähäri [this message]
2021-03-10 19:49             ` Andy Kosela
2021-03-10 20:17               ` Ken Thompson
2021-03-10 20:30                 ` Rob Pike
2021-03-11  3:54                   ` George Michaelson
2021-03-11  4:57                     ` Will Senn
2021-03-10  2:34         ` Nemo Nusquam
2021-03-12  2:48         ` 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=20210310183733.GA14019@box.prefix.duckdns.org \
    --to=andreas.kahari@abc.se \
    --cc=tuhs@tuhs.org \
    --cc=usotsuki@buric.co \
    /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).