The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] Less -- was Termcap vs terminfo
Date: Mon, 12 Jan 2015 16:25:07 -0500	[thread overview]
Message-ID: <CAC20D2M6Fag5Woz1crqsfgpQ54-eGG2q-5VHRG76N1h=yuC==Q@mail.gmail.com> (raw)
In-Reply-To: <1421094861.3387032.212981065.1F9F4427@webmail.messagingengine.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1360 bytes --]

On Mon, Jan 12, 2015 at 3:34 PM, <random832 at fastmail.us> wrote:
>
>
> In principle, the functions "detachable terminal session", "terminal
> session multiplexer", and "terminal with scrollback", and "translator
> from a common VT100 superset to whatever the hell the user is using"
> could be four separate programs.



​To quote Rob and Brian from the "cat -v" paper: [
http://harmful.cat-v.org/cat-v/unix_prog_design.pdf]

​

Separate programs are not always better than wider options; which is better
depends on the problem.
Whenever one needs a way to perform a new function, one faces the choice of
whether to add a new option
or write a new program (assuming that none of the programmable tools will
do the job conveniently). The
guiding principle for making the choice should be that each program does
one thing. Options are appropriately
added to a program that already has the right functionality. If there is no
such program, then a new
program is called for. In that case, the usual criteria for program design
should be used: the program should
be as general as possible, its default behavior should match the most
common usage, and it should cooperate
with other programs.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20150112/fb4d7542/attachment.html>


  reply	other threads:[~2015-01-12 21:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-11  5:20 Doug McIlroy
2015-01-11 17:08 ` Jacob Ritorto
2015-01-11 19:40 ` Brantley Coile
2015-01-11 21:27   ` Dave Horsfall
2015-01-11 22:10     ` Brantley Coile
2015-01-12 15:32   ` Clem Cole
2015-01-12 19:38 ` random832
2015-01-12 19:44   ` Jacob Ritorto
2015-01-12 19:52     ` cowan
2015-01-12 19:53     ` Kurt H Maier
2015-01-12 20:34     ` random832
2015-01-12 21:25       ` Clem Cole [this message]
2015-01-15  4:32         ` Jacob Ritorto

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='CAC20D2M6Fag5Woz1crqsfgpQ54-eGG2q-5VHRG76N1h=yuC==Q@mail.gmail.com' \
    --to=clemc@ccc.com \
    /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).