From: nobozo@gmail.com (Forrest, Jon)
Subject: [TUHS] pre-more pager?
Date: Wed, 8 Nov 2017 12:11:12 -0800 [thread overview]
Message-ID: <0df737f5-f356-7252-2404-1acc43e52adb@gmail.com> (raw)
In-Reply-To: <20171108200222.B6A6F18C0B9@mercury.lcs.mit.edu>
On 11/8/2017 12:02 PM, Noel Chiappa wrote:
> > From: Jon Forrest
>
> > In the early days of Unix I was told that it wasn't practical to write a
> > pager because such a thing would have to run in raw mode in order to
> > process single letter commands, such as the space character for going on
> > to the next page. Since raw mode introduced a significant amount of
> > overhead on already overtaxed machines, it was considered an anti-social
> > thing to do.
>
> Something sounds odd here.
I agree, now that I think about it. I do remember being told not to
write such a thing, due to the load it would cause. Maybe John Nagle,
who had the cube next to mine, might remember better.
> Overhead was definitely an issue with EMACS on Multics, where waking up a
> process on each character of input was significant. I think Bernie's Multics
> EMACS document discusses this. I'm pretty sure they used the Telnet RCTE
> option to try and minimize the overhead.
I remember ~40 students at UCSB trying to run 'vi' on a Vax 780 with 4MB of
RAM. Between the lack of memory and the overhead of raw mode, it wasn't
a pretty sight.
Jon
next prev parent reply other threads:[~2017-11-08 20:11 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 [this message]
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
-- 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=0df737f5-f356-7252-2404-1acc43e52adb@gmail.com \
--to=nobozo@gmail.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).