From: ed@flat5.net (Ed)
Subject: [TUHS] Unix taste
Date: Sat, 02 Aug 2014 09:07:10 -0700 [thread overview]
Message-ID: <p242lk9il46fkltjy7pipoob.1406995519672@email.android.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1381 bytes --]
Arrow keys? Vi does arrow keys? But then I'd have to move my hand from home.
That's not vi.
--
Ed Skinner, ed at flat5.net, http://www.flat5.net/
-------- Original message --------
From: Doug McIlroy <doug@cs.dartmouth.edu>
Date: 08/02/2014 8:38 AM (GMT-07:00)
To: tuhs at minnie.tuhs.org,lm at mcvoy.com
Subject: Re: [TUHS] Unix taste
> So Doug, ed? Or what?
Yes, ed for small things. It loads instantly and works in the
current window without disturbing it. And it has been ingrained
in my fingers since Multics days.
But for heavy duty work, I use sam, in Windows as well as Linux.
Sam marries ed to screen editing much more cleanly than vi.
It has recursive global commands and infinite undo. Like qed
(whence came ed's syntax) and Larry's xvi it can work on
several files (or even several areas in one file) at once.
I would guess that a vi adept would miss having arrow keys
as well as the mouse, but probably not much else. Sam offers
one answer for my question about examples of taste reigning
in featurism during the course of Unix evolution.
Doug
_______________________________________________
TUHS mailing list
TUHS at minnie.tuhs.org
https://minnie.tuhs.org/mailman/listinfo/tuhs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20140802/9c3b641e/attachment.html>
next reply other threads:[~2014-08-02 16:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-02 16:07 Ed [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-08-14 4:34 Norman Wilson
2014-08-14 4:49 ` A. P. Garcia
2014-08-08 3:27 Noel Chiappa
2014-08-08 2:12 Doug McIlroy
2014-08-02 15:38 Doug McIlroy
2014-08-02 16:07 ` 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=p242lk9il46fkltjy7pipoob.1406995519672@email.android.com \
--to=ed@flat5.net \
/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).