The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] Fwd: Old Unix manuals, TMs, etc
Date: Wed, 23 May 2018 12:03:34 -0700	[thread overview]
Message-ID: <CAC20D2MNkiWykN4m-g1v2vPbj7NS11Vj7w7q06HEbTd5C94wfA@mail.gmail.com> (raw)
In-Reply-To: <ec3104fc-3713-4fbe-b3b8-223f3cb41568@spamtrap.tnetconsulting.net>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1884 bytes --]

Grant - the troff input for all of those titles you listed should be in the
/usr/doc directory in the V6 or V7 archives that Warren has.   It's pretty
easy to push them through groff, you may have to tweak the input a little
though.   Contact me off list if you still need help,

Clem
ᐧ

On Wed, May 23, 2018 at 11:47 AM, Grant Taylor via TUHS <
tuhs at minnie.tuhs.org> wrote:

> On 05/23/2018 12:39 PM, Mike Markowski wrote:
>
>> I contacted Mel and hope to hear back.  …
>> …  Someone else might have already been in touch,  …
>>
>
> I emailed Mel directly and expressed interest in the following books:
>
>  · The M4 Marco Processor
>  · SED - A Non-Interactive Text Editor
>  · Awk - A pattern Scanning and Processing Language
>  · Yacc: Yet Another Compiler-Compiler
>  · RATFOR - A Preprocessor for a Rational Fortran
>
> Here's my comment as to why I'm interested in the aforementioned titles.
>
> I am interested in the following items if they are unclaimed.  I used sed
>> and awk on a daily basis.  I also have what some would consider an
>> unhealthy interest in M4.  I've written things in M4 that some might say
>> become their own markup language for config files.  Which is reminiscent of
>> what I think YACC is supposed to be, hence my interest in that Technical
>> Memorandum, to learn more.  RATFOR, likewise.
>>
>
> The only title that I'd *really* /like/ to get my hands on is "The M4
> Macro Processor".  (See aforementioned unhealthy interest in M4.)
>
> I'm quite happy to share with the community.  I just want to save the
> materials from the bin if nobody else claims them.
>
> Note:  I've not heard anything back from Mel yet.
>
>
>
> --
> Grant. . . .
> unix || die
>
>
ᐧ
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180523/3cf6624c/attachment.html>


  reply	other threads:[~2018-05-23 19:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-23  3:38 Warren Toomey
2018-05-23 17:53 ` arnold
2018-05-23 18:31   ` Arthur Krewat
2018-05-23 18:39   ` Mike Markowski
2018-05-23 18:47     ` Grant Taylor
2018-05-23 19:03       ` Clem Cole [this message]
2018-05-23 18:49     ` 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=CAC20D2MNkiWykN4m-g1v2vPbj7NS11Vj7w7q06HEbTd5C94wfA@mail.gmail.com \
    --to=clemc@ccc.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).