From: Clem Cole <clemc@ccc.com>
To: KenUnix <ken.unix.guy@gmail.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Trying to date "A Supplemental Document For Awk"
Date: Wed, 28 Jun 2023 14:38:40 -0400 [thread overview]
Message-ID: <CAC20D2Mdgvbj+uWr+RbcyWx=6D=RAgpytfcRC3G_NPkSHGFYNg@mail.gmail.com> (raw)
In-Reply-To: <CAJXSPs_5E3tONF82m1qdPyyE2YXfDRdRof31xtnBSxgZRBz_wQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2607 bytes --]
Download the file and make sure you save it in "UNIX" format, not DOS (
*i.e.* newline delimited not the nasty <CR><LF> cruft) -- (if you are not
sure how to do that running the dos2unix(1) command will assure it's was
not unix format when you are done).
% file awkdoc
awkdoc: troff or preprocessor input text, ASCII text
% man groff
We'll leave it to you to figure out which switches for troff/groff and
macro package (hint: try the head(1) command to peak at the first few lines
-- there are three likely choices, but it's pretty obvious since the same
one as most V7 documents).
FWIW: If you got a copy of Kernighan and Pike's - "The Unix Programming
Environment" [ISBN 0-13-937699-2] which is available at most retailers.
You can read Chapter 9 for this question. Although, given so many of the
questions you seem to like to ask here, please consider doing all the
exercises in the entire book.
ᐧ
On Wed, Jun 28, 2023 at 2:04 PM KenUnix <ken.unix.guy@gmail.com> wrote:
> Guys,
>
> It's been too long. What would I use to compile this man page source?
>
> I do remember some option switches are required. Yes?
>
> Thanks
>
>
> On Wed, Jun 28, 2023 at 1:49 PM Adam Sampson <ats@offog.org> wrote:
>
>> On Wed, Jun 28, 2023 at 09:26:02AM +0300, Aharon Robbins wrote:
>> > Attached is "A Supplemental Document For Awk". This circulated on
>> > USENET in the 80s. My copy is dated January 18, 1989, but I'm sure
>> > it's older than that.
>>
>> In the utzoo Usenet archive, there are two versions of this document and
>> a few mentions of it...
>>
>> John Pierce posted to comp.unix.questions on 1989-04-02, saying he'd
>> written it "four or five years ago".
>>
>> Stu Heiss, in comp.unix.questions on 1989-03-06, said it was "posted to
>> net.sources 18 Jun 86 with message-id 238@sdchema.sdchem.uucp".
>> Unfortunately this isn't in the utzoo archive or the net.sources.mbox
>> in archive.org's Usenet Historical Collection.
>>
>> A copy identical to yours was posted by Jim Harkins to
>> comp.unix.questions on 1990-03-29.
>>
>> There's a later version, fixing a typo and some formatting and adding a
>> mention of \f and \b in printf, which was posted by Brian Kantor to
>> comp.doc on 1987-10-11 -- I've attached this. The same file (with two
>> .bps commented out) was reposted in comp.unix.questions on 1989-11-16 by
>> Francois-Michel Lang.
>>
>> Thanks,
>>
>> --
>> Adam Sampson <ats@offog.org> <http://offog.org/>
>>
>
>
> --
> End of line
> JOB TERMINATED -->> Okey Dokey, OK Boss
>
>
>
[-- Attachment #2: Type: text/html, Size: 5062 bytes --]
next prev parent reply other threads:[~2023-06-28 18:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 6:26 [TUHS] " Aharon Robbins
2023-06-28 6:45 ` [TUHS] " arnold
2023-06-28 17:48 ` Adam Sampson
2023-06-28 18:03 ` KenUnix
2023-06-28 18:38 ` Clem Cole [this message]
2023-06-28 23:47 ` Greg 'groggy' Lehey
2023-06-29 1:59 ` Stuff Received
2023-06-29 6:27 ` segaloco via TUHS
2023-06-29 6:41 ` Andrew Hume
2023-06-29 6:45 ` Noel Hunt
2023-06-29 6:48 ` Andrew Hume
2023-06-29 6:50 ` arnold
2023-06-29 6:44 ` Noel Hunt
2023-06-29 14:02 ` G. Branden Robinson
2023-06-29 13:45 ` G. Branden Robinson
2023-06-29 13:34 ` G. Branden Robinson
2023-06-29 13:47 ` Rich Salz
2023-06-29 19:03 ` Steffen Nurpmeso
2023-06-29 1:04 ` Bakul Shah
2023-06-29 0:26 ` Jeremy C. Reed
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='CAC20D2Mdgvbj+uWr+RbcyWx=6D=RAgpytfcRC3G_NPkSHGFYNg@mail.gmail.com' \
--to=clemc@ccc.com \
--cc=ken.unix.guy@gmail.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).