From: krewat@kilonet.net (Arthur Krewat)
Subject: [TUHS] pre-more pager?
Date: Wed, 8 Nov 2017 14:06:46 -0500 [thread overview]
Message-ID: <9dc0fdd2-d4d4-8375-2117-a744e1b8f88a@kilonet.net> (raw)
In-Reply-To: <ADEC3475-4CF1-4B0C-AEF4-533CAF46A3F9@gmail.com>
^S (stop) and ^Q (continue) at 1200 baud or less worked OK, especially
on paper terminals ;) -- (Clem just beat me to it)
head and tail would work too (although I'm not sure they existed at that
time, I'm no expert):
cat filename | head -20 # get the first page.
cat filename | head -40 | tail -20 # get the second page.
<ad infinitum>
etc.
On 11/8/2017 1:54 PM, Will Senn wrote:
> Hi,
>
> In looking around the system v7 environment, I don't see a more command anywhere. I downloaded, converted, and attached 1bsd, 2bsd, and finally 3bsd and it was there that I found source for more... 3bsd looks like it's for VAX, not PDP-11, and it doesn't want to compile (looking for some externs that I gather are part of the distro's clib).
>
> I may jump ship on V7 and head over to 2.9BSD, which, as I understand it, is a V7 with fixes and these kind of additional tools...
>
> 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 :).
>
> Thanks,
>
> Will
>
> Sent from my iPhone
>
next prev parent reply other threads:[~2017-11-08 19:06 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 [this message]
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
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=9dc0fdd2-d4d4-8375-2117-a744e1b8f88a@kilonet.net \
--to=krewat@kilonet.net \
/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).