From: Warren Toomey <wkt@tuhs.org>
To: Doug McIlroy <doug@cs.dartmouth.edu>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] Rivers, the ragged right, and BCPL roff (was: Spooky action at a distance in line adjustment...sometimes)
Date: Mon, 2 Jul 2018 09:20:23 +1000 [thread overview]
Message-ID: <20180701232023.GB17726@minnie.tuhs.org> (raw)
In-Reply-To: <201807010223.w612Nv7P094105@tahoe.cs.Dartmouth.EDU>
On Sat, Jun 30, 2018 at 10:23:57PM -0400, Doug McIlroy wrote:
>I edited the v7 manual and I believe I proofread every man page. How
>could I have overlooked the misbehavior of the .li request*, which was
>even then not in the reference manual's list of n/troff requests?
>doug
>
>* .li causes the next line to be read literally, even if it begins
>with a dot.
Slightly Unix related, .li is in the version of roff which I wrote in
a C-like language for the PDP-7 version of Unix:
https://github.com/DoctorWkt/h-compiler/blob/master/roff/wktroff.c
https://github.com/DoctorWkt/h-compiler/blob/master/roff/roff_manual
https://github.com/DoctorWkt/h-compiler
Cheers, Warren
prev parent reply other threads:[~2018-07-01 23:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-01 2:23 Doug McIlroy
2018-07-01 23:20 ` Warren Toomey [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=20180701232023.GB17726@minnie.tuhs.org \
--to=wkt@tuhs.org \
--cc=doug@cs.dartmouth.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).