From: Martin Neubauer <m.ne@gmx.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] troff ignoring .eo/.ec after first time
Date: Wed, 21 Nov 2007 23:39:49 +0100 [thread overview]
Message-ID: <20071121223949.GA862@shodan.homeunix.net> (raw)
In-Reply-To: <3950E912-6C70-4726-B16D-79008B73FE00@mac.com>
ms(6) says:
Many nroff and troff
requests are unsafe in conjunction with this package, but
the following requests may be used with impunity after the
first .PP: `.bp', `.br', `.sp', `.ls', `.na'.
Maybe this helps,
Martin
* Pietro Gagliardi (pietro10@mac.com) wrote:
> Hello. Try this:
>
> tbl /n/sources/contrib/pietro/plan9prog.ms | troff -ms | page
>
> On about the third page, some code begins, but at the print()
> statement at the end there is some strangeness. If you look inside
> the .ms file, there are some .eo and .ec requests. .eo turns off \x
> and .ec turns it back on. But why is it ignored after that first
> page, which works correctly?
next prev parent reply other threads:[~2007-11-21 22:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 22:06 Pietro Gagliardi
2007-11-21 22:39 ` Martin Neubauer [this message]
2007-11-22 16:55 ` Russ Cox
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=20071121223949.GA862@shodan.homeunix.net \
--to=m.ne@gmx.net \
--cc=9fans@cse.psu.edu \
/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).