From: norman@oclsc.org (Norman Wilson)
Subject: [TUHS] basic tools / Universal Unix
Date: Wed, 01 Nov 2017 18:51:25 -0400 [thread overview]
Message-ID: <1509576688.7596.for-standards-violators@oclsc.org> (raw)
Arnold:
> OK, that I can understand. It's ages since I played with
> readline, but I think you can preload the buffer it works on
> (bash does that, no?) so ed + readline could be made to work
> that way.
====
Or, if you have moved beyond the era of simulated glass
teletypes on graphics screens, you could do the editing
in the terminal (program).
It's a real shame the mux/9term way of doing things never
caught on. I suppose it is because so many people are
wedded to programs that require cursor addressing; I'm
glad I never succumbed to that.
I use ed (or its cousin qed a la Toronto) for simple stuff.
Mostly I'll use the traditional commands, but sometimes
I will, in mux/9term style, print a line with p, type
c, edit the line on the screen, pick it up and send it,
type . return.
And of course I can do that sort of thing with any program,
whether or not it is compiled with some magic library.
All this is something of a matter of taste, but I have
sometimes amazed (in a good way) my colleagues with it.
Norman Wilson
Toronto ON
next reply other threads:[~2017-11-01 22:51 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 22:51 Norman Wilson [this message]
2017-11-01 23:09 ` Lyndon Nerenberg
2017-11-02 20:29 ` Grant Taylor
-- strict thread matches above, loose matches on Subject: below --
2017-11-15 14:06 Noel Chiappa
2017-11-15 17:12 ` Ralph Corderoy
2017-11-15 17:47 ` Larry McVoy
2017-11-15 18:40 ` Bakul Shah
2017-11-15 19:58 ` Larry McVoy
2017-10-31 19:23 Norman Wilson
2017-10-30 21:40 Noel Chiappa
2017-10-30 14:16 Noel Chiappa
2017-10-30 14:40 ` Clem Cole
2017-10-30 15:23 ` Arthur Krewat
2017-10-30 20:56 ` Dave Horsfall
2017-10-31 10:50 ` Ronald Natalie
2017-11-01 3:23 ` Dave Horsfall
2017-11-01 13:25 ` Tim Bradshaw
2017-11-16 1:17 ` Dario Niedermann
2017-11-15 1:25 ` Nemo
2017-11-15 2:10 ` Will Senn
2017-11-15 2:16 ` Larry McVoy
2017-11-15 2:37 ` Warner Losh
2017-11-15 3:07 ` Will Senn
2017-11-15 16:13 ` Arthur Krewat
2017-11-15 16:23 ` Arthur Krewat
2017-11-15 16:48 ` Clem Cole
2017-11-15 18:13 ` Bakul Shah
2017-11-15 19:01 ` Clem Cole
2017-11-15 9:58 ` Andy Kosela
2017-11-15 11:42 ` Ralph Corderoy
2017-11-01 14:05 ` Ralph Corderoy
2017-11-01 16:42 ` arnold
2017-11-01 17:17 ` Ralph Corderoy
2017-11-01 18:03 ` Dan Cross
2017-11-01 18:06 ` arnold
2017-11-01 20:16 ` Bakul Shah
2017-11-01 20:37 ` arnold
2017-11-01 21:04 ` Bakul Shah
2017-11-02 0:05 ` Chet Ramey
2017-11-02 0:10 ` Ralph Corderoy
2017-10-31 16:43 ` Don Hopkins
2017-11-02 17:48 ` Paul Winalski
2017-10-30 21:50 ` Charles Anthony
2017-10-18 23:03 Doug McIlroy
2017-10-19 3:53 ` Random832
2017-10-19 14:33 ` Steffen Nurpmeso
2017-10-19 14:41 ` Random832
2017-10-19 21:03 ` Steffen Nurpmeso
2017-10-20 19:54 ` Steffen Nurpmeso
2017-10-19 14:32 ` Steffen Nurpmeso
2017-10-16 17:52 Clem Cole
2017-10-16 18:54 ` Dan Cross
2017-10-17 13:51 ` Tony Finch
2017-10-17 20:22 ` Steffen Nurpmeso
2017-10-16 20:05 ` Bakul Shah
2017-10-30 0:55 ` Ralph Corderoy
2017-10-30 2:54 ` Bakul Shah
2017-10-30 14:05 ` Ralph Corderoy
2017-10-16 20:39 ` Andy Kosela
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=1509576688.7596.for-standards-violators@oclsc.org \
--to=norman@oclsc.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).