The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "MIT Book Club" <martymcg@fastmail.com>
To: KenUnix <ken.unix.guy@gmail.com>, "Pete Wright" <tuhs@tuhs.org>
Subject: [TUHS] Re: Unix v7 programs to share
Date: Fri, 03 Mar 2023 10:03:43 -0500	[thread overview]
Message-ID: <90b9dbd9-6b82-4179-8a5e-fff197d0e740@app.fastmail.com> (raw)
In-Reply-To: <CAJXSPs-Vn947sEY=t8V0rrn51ojTECWqE57PWdKJhF5Yc7DzMw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1222 bytes --]

Ken U Guy,

   thanks especially for the Text Editor.    i'm sharing it in our community who think a word processor is.

=*+[]+  Marty McGowan        +1 908 230-3739
The MIT Book Club, Princeton and Northern NJ <https://applemcg.github.io/#MIT%20Book%20Club>
 <https://applemcg.github.io/#MIT%20Book%20Club>






On Thu, Mar 2, 2023, at 07:45, KenUnix wrote:
> Unix v7 programs to share
> 
> 
> With all your help I thought I would share a couple of programs I had a hand in.
> 
> more.c is like 'more' for Linux. more abc.txt or cat abc.txt | more or ls -l | more
> pg.c is a 'pager' program. pg abc.txt def.txt
> cls. is a clear screen home cursor program using VT100 codes. It works on
>       the console or telnet or putty.
> 
> All can be compiled and placed in /usr/bin
>   cc -o /usr/bin/cls cls.c
>   cc -o /usr/bin/more more.c
>   cc -o /usr/bin/pg pg.c
> 
> https://drive.google.com/file/d/1LR3Q11sGADXuqA2C2c2gEKmJOrsXA8QC/view?usp=sharing
> https://drive.google.com/file/d/1_IUnyPwsRvYMAuqO9xb8Z8MZDbKLST70/view?usp=sharing
> https://drive.google.com/file/d/1t88SNnJjWIbPrGuTFfFZM-7qKhD6AS6S/view?usp=sharing
> 
> More to  come.
> 
> Ken
> 
> --
> 
> WWL 📚
> 
> 

[-- Attachment #2: Type: text/html, Size: 3487 bytes --]

      reply	other threads:[~2023-03-03 15:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-02 12:45 [TUHS] " KenUnix
2023-03-03 15:03 ` MIT Book Club [this message]

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=90b9dbd9-6b82-4179-8a5e-fff197d0e740@app.fastmail.com \
    --to=martymcg@fastmail.com \
    --cc=ken.unix.guy@gmail.com \
    --cc=martymcgowan@alum.mit.edu \
    --cc=tuhs@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).