From: "Ron Natalie" <ron@ronnatalie.com>
To: "tuhs@tuhs.org" <tuhs@tuhs.org>
Subject: [TUHS] Re: Old troff files (1988-2007)
Date: Wed, 09 Oct 2024 21:02:12 +0000 [thread overview]
Message-ID: <em245107c5-e0a1-4976-aef2-11771922332d@60fbdfec.com> (raw)
In-Reply-To: <ema62b50de-925b-4e29-84be-f13f910649f2@60fbdfec.com>
I got a chuckle because apparently an old quote of mine is enshrined in
the GROFF documentation (under the debugging section):
Standard troff voodoo, just put a power of two backslashes in front of
it until it works and if you still have problems add a \c. — Ron Natalie
Thanks, G. Branden Robinson, for calling it to my attention.
More nroff fun and games: My first job out of college was working on a
restricted government project on RSX-11/M. I’d been doing various
UNIX and n/troff stuff for years at JHU.
The QA people decided to go all PWB on this project using SCCS etc…
I knew that Denis Mumaugh at the NSA had written nroff macros to do
classification markings automatically.
I asked for a copy, but he couldn’t figure out how to get a tape to me.
I reimplemented it myself. Originally, I had the idea of processing
each marked paragraph into a diversion but
that was problematic. I then just output the footer and then “reverse
fed” the paper back to the top to add the top classification. Of
course, you had to run your nroff via col to
get it to print right.
I also fixed the line printer spooler to catch classification markings
and mark them pages appropriately as well. All this I did while
waiting the 11 months for my ‘beyond TS’ clearance to arrive.
Seems like everybody on the project failed their polygraph the first
time. Examiner must have had a hard seat on the bus from the east
coast.
This was also the project where I had this exchange:
Bernie: What’s all this Bell System crud in the editor?
Me: It’s UNIX. It’s all Bell System crud.
I walk around to his terminal and see this:
$ 1
One Bell System. It works.
$ 1
One Bell System. It works.
Me: You’re not in the editor, Bernie.
After that the /usr/bin/1 command was changed to
echo “You’re not in the editor, Bernie.”
next prev parent reply other threads:[~2024-10-09 21:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 21:42 [TUHS] " Jacobson, Doug W [E CPE] via TUHS
2024-10-04 21:50 ` [TUHS] " Lyndon Nerenberg (VE7TFX/VE6BBM)
2024-10-04 21:52 ` Jacobson, Doug W [E CPE] via TUHS
2024-10-04 22:10 ` Bakul Shah via TUHS
2024-10-04 23:01 ` Clem Cole
2024-10-04 23:16 ` Clem Cole
2024-10-05 0:14 ` G. Branden Robinson
2024-10-05 4:09 ` Peter Yardley
2024-10-05 13:14 ` Clem Cole
2024-10-05 22:22 ` G. Branden Robinson
[not found] ` <CAC20D2NgmzDxhQu5P5hjrZ3ciSv=KayiUg8GwsFRpu0wPasprw@mail.gmail.com>
2024-10-06 5:53 ` [TUHS] Why groff ms doesn't completely support historical documents G. Branden Robinson
2024-10-06 12:54 ` [TUHS] Re: Old troff files (1988-2007) Jaap Akkerhuis
2024-10-06 15:11 ` G. Branden Robinson
2024-10-06 16:21 ` Ron Natalie
2024-10-09 21:02 ` Ron Natalie [this message]
2024-10-07 14:50 ` Leah Neukirchen
2024-10-08 6:45 ` G. Branden Robinson
2024-10-08 10:33 ` Jacobson, Doug W [E CPE] via TUHS
2024-10-08 10:49 ` G. Branden Robinson
2024-10-08 11:24 ` Jacobson, Doug W [E CPE] via TUHS
2024-10-16 21:40 ` Anton Shepelev
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=em245107c5-e0a1-4976-aef2-11771922332d@60fbdfec.com \
--to=ron@ronnatalie.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).