From: cowan@mercury.ccil.org (John Cowan)
Subject: [TUHS] Unix taste
Date: Sat, 2 Aug 2014 12:07:04 -0400 [thread overview]
Message-ID: <20140802160704.GG15007@mercury.ccil.org> (raw)
In-Reply-To: <201408021538.s72Fcs7o021169@coolidge.cs.dartmouth.edu>
Doug McIlroy scripsit:
> 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.
I use ex exclusively, being willing to trade a little standardosity for
a little more user-friendliness. I have no trouble switching to ed if
necessary (as when /usr is not mounted, though nowadays /usr is typically
on the root file system). It is certainly ingrained in my fingers;
I'm using it to write this email. I usually write scripts for ed rather
than ex, as I usually write shell scripts for a Posix shell, not for bash.
Very occasionally I switch to vi mode, mostly so I can use the % key
when editing Lisp, or to edit a highly repetitive line (try changing
"one one one one one one one one one" to "one one one one one two one
one one one" with ed/ex alone!) The only vi commands I know are h, j,
k, l, x, i, %, and most importantly Q, which gets me back to ex mode.
My answer to "What's your IDE?" is "Console running a bunch of 'ex'
tabs and one shell tab for typing 'make'."
> But for heavy duty work, I use sam, in Windows as well as Linux.
I've tried to switch to sam several times, but so far without success.
The lack of arrow keys is annoying for close-up editing, and since I use
Windows as a terminal to hack remote Solaris or Linux systems, the lack
of -r in the Windows version of sam is very annoying.
> 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.
Agreed on all points. See esr's "A Tale of Five Editors" at
<http://www.catb.org/esr/writings/taoup/html/ch13s02.html> (be sure to
click the "Next" link for his analysis). I contributed much of the sam
and acme/wily sections. (I know you've read this, since you are quoted
in it, but others here may not have.)
> 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.
"Reining in", please (peeve, peeve)
--
John Cowan http://www.ccil.org/~cowan cowan at ccil.org
Adam [...] did not want the apple for the apple's sake, he wanted it only
because it was forbidden. The mistake was not forbidding the serpent;
then he would have eaten the serpent. --Mark Twain
next prev parent 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 15:38 Doug McIlroy
2014-08-02 16:07 ` John Cowan [this message]
2014-08-02 16:07 Ed
2014-08-08 2:12 Doug McIlroy
2014-08-08 3:27 Noel Chiappa
2014-08-14 4:34 Norman Wilson
2014-08-14 4:49 ` A. P. Garcia
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=20140802160704.GG15007@mercury.ccil.org \
--to=cowan@mercury.ccil.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).