From: dave@horsfall.org (Dave Horsfall)
Subject: [TUHS] pre-more pager?
Date: Thu, 9 Nov 2017 09:47:58 +1100 (EST) [thread overview]
Message-ID: <alpine.BSF.2.21.1711090946511.4766@aneurin.horsfall.org> (raw)
In-Reply-To: <20171108200222.B6A6F18C0B9@mercury.lcs.mit.edu>
On Wed, 8 Nov 2017, Noel Chiappa wrote:
> But that's all second-order effects anyway. If one were using a serial
> line hooked up to a DZ (and those were common - DH's were _much_ more
> expensive, so poor places like my lab at MIT used DZ's), then _every
> character printed_ caused an interrupt. So the overhead from printing
> each screen-ful of text was orders of magnitude greater than the
> overhead of the user's input to get the next screen.
Looxury! We had to make do with DJ-11s...
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
next prev parent reply other threads:[~2017-11-08 22:47 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 20:02 Noel Chiappa
2017-11-08 20:11 ` Forrest, Jon
2017-11-10 5:26 ` Random832
2017-11-10 7:31 ` Otto Moerbeek
2017-11-08 20:18 ` Clem Cole
2017-11-08 20:28 ` Ron Natalie
2017-11-08 22:47 ` Dave Horsfall [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-11-09 16:19 Norman Wilson
2017-11-09 16:48 ` Arthur Krewat
2017-11-09 17:19 ` Steve Nickolas
2017-11-09 18:15 ` Don Hopkins
2017-11-09 18:26 ` Arthur Krewat
2017-11-09 13:33 Doug McIlroy
2017-11-08 22:58 Doug McIlroy
2017-11-08 22:02 Paul Ruizendaal
2017-11-08 22:20 ` Will Senn
2017-11-08 20:28 Noel Chiappa
2017-11-08 19:23 Noel Chiappa
2017-11-08 18:54 Will Senn
2017-11-08 18:59 ` Clem Cole
2017-11-08 19:06 ` Arthur Krewat
2017-11-08 19:31 ` Jeremy C. Reed
2017-11-08 22:43 ` Dave Horsfall
2017-11-08 22:47 ` Arthur Krewat
2017-11-08 23:21 ` Dave Horsfall
2017-11-09 4:38 ` Will Senn
2017-11-09 13:18 ` Dan Cross
2017-11-09 14:29 ` Will Senn
2017-11-09 20:53 ` Dave Horsfall
2017-11-10 0:15 ` Arthur Krewat
2017-11-10 2:14 ` Ralph Corderoy
2017-11-08 19:12 ` Bakul Shah
2017-11-08 19:22 ` Random832
2017-11-08 21:18 ` Will Senn
2017-11-08 21:59 ` Ron Natalie
2017-11-08 22:00 ` Clem Cole
2017-11-08 22:18 ` Will Senn
2017-11-09 2:01 ` Steve Johnson
2017-11-09 2:16 ` Lyndon Nerenberg
2017-11-08 19:29 ` Forrest, Jon
2017-11-08 19:43 ` Ron Natalie
2017-11-08 21:03 ` Mark Green
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=alpine.BSF.2.21.1711090946511.4766@aneurin.horsfall.org \
--to=dave@horsfall.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).