The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: cowan@mercury.ccil.org (John Cowan)
Subject: [TUHS] PWB contributions
Date: Mon, 9 Nov 2015 09:44:16 -0500	[thread overview]
Message-ID: <20151109144416.GA13422@mercury.ccil.org> (raw)
In-Reply-To: <201511091358.tA9Dw35f010741@coolidge.cs.Dartmouth.EDU>

Doug McIlroy scripsit:

> And to set a world benchmark for software bloat. For a good time try
>         less --help | wc

I disagree entirely: it's a matter of how you see less.  For me it is
roughly comparable to ed (and indeed the primary documentation is about
the same size).  Both have the function of letting you inspect, in ways
not predictable in advance, the contents of a file.  Ed also allows
you to modify the file, whereas less has a more convenient interface
for dealing with pipeline output, and has single-keystroke convenience
commands, notably space.

(IWBNI ed had a switch to make it read stdin into the buffer and then
read commands from /dev/tty.  Obviously a wrapper script could achieve
this easily.)

Disclaimer:  I actually use ex, not ed: I'm willing to trade off a
litttle less standardosity for a little more convenience.  That also
of a minimal subset of vi commands when dealing with code that contains
highly repetitive strings, notably Lisp parentheses.

-- 
John Cowan          http://www.ccil.org/~cowan        cowan at ccil.org
"Repeat this until 'update-mounts -v' shows no updates.
You may well have to log in to particular machines, hunt down
people who still have processes running, and kill them."



  parent reply	other threads:[~2015-11-09 14:44 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-09  1:39 Doug McIlroy
2015-11-09  1:48 ` John Cowan
2015-11-09  2:12 ` Clement T. Cole
2015-11-09  2:54   ` Win Treese
2015-11-09  2:58     ` Win Treese
2015-11-09  3:36       ` Clem cole
2015-11-09  3:51         ` Clem cole
2015-11-09 15:40         ` Dave Horsfall
2015-11-09 15:54           ` Clem Cole
2015-11-09 22:12         ` Mary Ann Horton
2015-11-09  3:38       ` Random832
2015-11-09  4:50         ` Clem cole
2015-11-09 13:58   ` Doug McIlroy
2015-11-09 14:02     ` Ronald Natalie
2015-11-09 14:44     ` John Cowan [this message]
2015-11-10 20:26     ` [TUHS] A portrait of cut(1) (was: PWB contributions) markus schnalke
2015-11-10 22:10       ` Clem Cole
2015-11-10 23:10       ` Andy Kosela
2015-11-10 23:12         ` John Cowan
2015-11-10 23:34           ` Larry McVoy
2015-11-10 23:39             ` John Cowan
2015-11-11  0:16       ` [TUHS] A portrait of cut(1) Random832
2015-11-11 12:23         ` markus schnalke
2015-11-09 22:23   ` [TUHS] PWB contributions Jeremy C. Reed
2015-11-10  4:11     ` Random832
2015-11-09  4:44 ` Larry McVoy
2015-11-09  4:51   ` John Cowan
2015-11-09  5:07     ` Larry McVoy
2015-11-09  5:09       ` Larry McVoy
2015-11-09  5:16         ` John Cowan
2015-11-09  5:16         ` Leonardo Taccari
2015-11-09  2:14 Doug McIlroy
2015-11-09  2:32 ` 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=20151109144416.GA13422@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).