The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: markwgreen@rogers.com (Mark Green)
Subject: [TUHS] pre-more pager?
Date: Wed, 8 Nov 2017 16:03:01 -0500	[thread overview]
Message-ID: <D6AF632A-B4B3-4DEC-8C3A-8835CCAB402D@rogers.com> (raw)
In-Reply-To: <b85b76ea-8922-cb83-023f-1a9590de23af@gmail.com>

If I recall correctly there was a program called p on v6 unix that served as a pager. I think it was part of the standard distribution and not a local Toronto mod. 

Sent from my iPhone

> On Nov 8, 2017, at 2:29 PM, Forrest, Jon <nobozo at gmail.com> wrote:
> 
> 
> 
>> On 11/8/2017 10:54 AM, Will Senn wrote:
>> Hi,
> 
>> In the meantime, how did folks page through text like man sh and such
>> before more? I know how to view sections of text using sed and ed's ok for
>> paging file text (painful, but workable). I just can't seem to locate the
>> idiomatic way of keeping everything from constantly scrolling out of view!
>> Obviously, this isn't a problem on my mac as terminal works fine, but I
>> like to try to stay in character as a 1970 time traveling unix user :).
> 
> 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.
> 
> In 1977 and 1978 I worked at Ford Aerospace in the group that produced
> KSOS, which was a "secure" version of Unix (I didn't actually work on
> KSOS myself since I didn't have, nor want, a security clearance). Anyway,
> that group used some incredibly expensive HP terminals that contained
> enough local memory to contain most text files, the way we overcame the
> lack of a pager was to cat the file, and then page around in the local
> memory.
> 
> IIRC later versions of Unix added the ability to respond to a specific
> list of single characters without going into raw mode. Of course, that
> didn't help when full-screen editors like vi and the Rand editor came out.
> 
> Cordially,
> Jon Forrest
> 
> 
> 



  parent reply	other threads:[~2017-11-08 21:03 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2017-11-08 19:23 Noel Chiappa
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
2017-11-08 20:28 Noel Chiappa
2017-11-08 22:02 Paul Ruizendaal
2017-11-08 22:20 ` Will Senn
2017-11-08 22:58 Doug McIlroy
2017-11-09 13:33 Doug McIlroy
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

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=D6AF632A-B4B3-4DEC-8C3A-8835CCAB402D@rogers.com \
    --to=markwgreen@rogers.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).