From: "Sijmen J. Mulder" <ik@sjmulder.nl>
To: Don Hopkins <don@donhopkins.com>
Cc: "tuhs@minnie.tuhs.org" <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] TUHS Digest, Vol 33, Issue 7
Date: Wed, 8 Aug 2018 15:51:07 +0200 [thread overview]
Message-ID: <20180808135106.D7441E4636@mailuser.nyi.internal> (raw)
In-Reply-To: <6EBCF9E5-4600-42D6-9F83-3E2966140540@donhopkins.com>
[-- Attachment #1: Type: text/plain, Size: 1384 bytes --]
> [...] totally overwhelms any aesthetic considerations of disliking
> prompts taking up a line (or insisting on a clear line before it -- I
> don’t understand why you would suggest such a straw man, which is not
> what I was advocating).
I totally understand what you're saying, but I hardly ever copy and
paste between terminals so it's just not an issue to me and then
my preference for a compact prompt and little whitespace prevails.
I'll give you that the clear line thing is personal and won't
necessarily apply to others. The "you'll want to" was misplaced.
> At least the 300 baud modem gave you time to ponder over those few lines
> before they scrolled off the screen. In that scenario, lines of text
> were precious, although the HP terminals charge by characters, not
> lines. But I don’t think anybody in their right mind uses terminals like
> that any more.
They charged per character? That's fascinating.
I'm too young to have worked with teletypes or terminals but to
experience what working over a slower connection would be like I wrote
a small pty program that throttles stdin and stdout to a given baud
rate:
https://github.com/sjmulder/trickle
It's probably nothing like the real thing but I found it interesting to
experience adapting to a slow terminal and to see things like pagers
update the screen step by step.
[-- Attachment #2: Type: text/html, Size: 3623 bytes --]
next prev parent reply other threads:[~2018-08-08 13:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2.1533693601.12251.tuhs@minnie.tuhs.org>
2018-08-08 12:10 ` Don Hopkins
2018-08-08 12:32 ` Sijmen J. Mulder
2018-08-08 12:59 ` Don Hopkins
2018-08-08 13:51 ` Sijmen J. Mulder [this message]
2018-08-08 14:45 ` Clem Cole
2018-08-08 14:56 ` Lawrence Stewart
2018-08-08 15:09 ` [TUHS] the distinct smell of light machine oil, was " Toby Thain
2018-08-08 17:38 ` Cornelius Keck
2018-08-08 19:14 ` Jim Geist
2018-08-08 20:44 ` Warner Losh
2018-08-09 5:14 ` arnold
2018-08-09 5:55 ` Jim Geist
2018-08-09 6:02 ` George Michaelson
2018-08-09 7:20 ` Dave Horsfall
2018-08-09 12:36 ` Warner Losh
2018-08-09 13:45 ` Michael Parson
2018-08-09 13:31 ` Clem Cole
2018-08-09 14:15 ` Derek Fawcus
2018-08-09 14:26 ` Eric Wayte
2018-08-10 11:37 ` Pete Turnbull
2018-08-10 11:37 ` Pete Turnbull
2018-08-10 16:24 ` Tom Ivar Helbekkmo via TUHS
2018-08-10 16:58 ` Pete Turnbull
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=20180808135106.D7441E4636@mailuser.nyi.internal \
--to=ik@sjmulder.nl \
--cc=don@donhopkins.com \
--cc=tuhs@minnie.tuhs.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).