The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: arnold@skeeve.com
To: segaloco@protonmail.com, gtaylor@tnetconsulting.net
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: early Unix papers, from Jim Joyce
Date: Mon, 07 Nov 2022 23:30:42 -0700	[thread overview]
Message-ID: <202211080630.2A86Ugc6004710@freefriends.org> (raw)
In-Reply-To: <18Dhvwn9Aec6LXGA5dkWkgVdxkprEOxlu7by1jOzuRHRz4Dd6095utKlbod1TRPI8R25Z06CXqkQO3ID9o6p4Cef7NvjI90-nrJsdH7ngy0=@protonmail.com>

Hi.

> Why Pascal is Not My Favorite Programming Language
>     - This sounds fun, not hard UNIX info, but fun

It's been around for a long time. A while back, I reconstituted
it, see https://www.github.com/arnoldrobbins/cstr100.

> A Typesetter-Independent TROFF
> - A ditroff-specific paper?  Can't say I've seen such a thing, would
> be interested in this one.  I know someone (can't recall name/email)
> in the GROFF mailing list seemed particularly excited about ditroff
> information that could be gleaned from the UNIX/TS 4.0 docs, this may
> be their golden carrot.

This is also around on the Internet.

If there's interest, I might could wheedle the original out of BWK.

> A Walk Through AWK
>     - Somewhere between the original AWK paper and the AWK book?

I missed this in the original list. I'd love to have a copy of it!

Arnold

  reply	other threads:[~2022-11-08  6:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02  3:46 [TUHS] " Rich Morin
2022-11-02  6:07 ` [TUHS] " Noel Chiappa
2022-11-02  7:32   ` [TUHS] Re: early Unix papers, from jim Joyce Michael Kjörling
2022-11-02 15:32   ` [TUHS] Re: early Unix papers, from Jim Joyce Grant Taylor via TUHS
2022-11-06 23:56     ` Rich Morin
2022-11-07 22:16       ` Grant Taylor via TUHS
2022-11-07 23:12         ` segaloco via TUHS
2022-11-08  6:30           ` arnold [this message]
2022-11-08 22:56             ` James Frew
2022-11-08 16:42           ` G. Branden Robinson
2022-11-17 20:42 Rich Morin

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=202211080630.2A86Ugc6004710@freefriends.org \
    --to=arnold@skeeve.com \
    --cc=gtaylor@tnetconsulting.net \
    --cc=segaloco@protonmail.com \
    --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).