The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Larry McVoy <lm@mcvoy.com>
To: Rob Pike <robpike@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] manual humour (was tunefs -m 5%)
Date: Tue, 9 Mar 2021 14:46:36 -0800	[thread overview]
Message-ID: <20210309224636.GY17304@mcvoy.com> (raw)
In-Reply-To: <CAKzdPgzzzE3vYcBgV4sSSsosBJSZbTPVdMHr3vgRk6Z727tOMw@mail.gmail.com>

ed was my goto over any modem, it's very undemanding in terms of characters
transferred.  Can't tell you how many times I've done

ed foo.c
/^some_function
20p
goto the line
c
whatever
.
w
q

So a lot of use so long as I was using dial up, some continued use when I was
doing bring up and the tty driver was all screwed up so you are typing at
some slow console.

Once performance wasn't an issue, it was vi all the time.  I did a year in
emacs, never warmed up to it, I know some people love it, I MUCH preferred
the way vi works.  So back to vi, some time spent in xvi because I was on
4MB main memory Sun machines so I made a version of libc that treated \n
like normal libc treats \0, then changed xvi so it used mmap(2) to map
the file instead of reading it in and strdup()ing every line.  I did that
because I was looking at performance logs and the very most I could fit 
into memory was 1/2 of what I could fit into memory with mmap().  That
2x bigger was a big deal to me, I was in out of those logs all the time.

xvi also had buffers, like emacs, you could be looking at 2 files at once
or 2 different regions of the same file.

Then vim came along and it had everything I wanted and I didn't have to
support it so I have been in vim since 1996 (that's the last time the
xvi source that I have was touched).

If things get wonky, ed still works, which is pleasant.  But 99.9% of the
time I'm in vim, I'm in it right now, typing this.  I still use mutt(1)
as my mail reader and I wacked it to drop me into vim.

On Wed, Mar 10, 2021 at 09:30:46AM +1100, Rob Pike wrote:
> I'm curious when people (other than me) erred and stopped saying that ed
> was the standard editor.
> 
> -rob

-- 
---
Larry McVoy            	     lm at mcvoy.com             http://www.mcvoy.com/lm 

  reply	other threads:[~2021-03-09 22:47 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 [this message]
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
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=20210309224636.GY17304@mcvoy.com \
    --to=lm@mcvoy.com \
    --cc=robpike@gmail.com \
    --cc=tuhs@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).