discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: "Anthony J. Bentley" <anthonyjbentley@gmail.com>
To: discuss@mdocml.bsd.lv
Subject: .LR macro
Date: Tue, 28 Dec 2010 21:58:40 -0700	[thread overview]
Message-ID: <4d1ac003.44842a0a.2155.4026@mx.google.com> (raw)

Hi,

This shows up in the Plan 9 manpage mk.1:

.PP
Seemingly appropriate input like
.B CFLAGS=-DHZ=60
is parsed as an erroneous attribute; correct it by inserting
a space after the first 
.LR = .
.PP

Output from Plan 9 troff:

       Seemingly appropriate input like CFLAGS=-DHZ=60 is parsed as an
       erroneous attribute; correct it by inserting a space after the first
       `='.

Mandoc cuts off the last bit:
       Seemingly appropriate input like CFLAGS=-DHZ=60 is parsed as an
       erroneous attribute; correct it by inserting a space after the first

OpenBSD's (ancient) groff displays the same as mandoc.

--
Anthony J. Bentley
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

             reply	other threads:[~2010-12-29  4:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-29  4:58 Anthony J. Bentley [this message]
2010-12-29  9:47 ` Kristaps Dzonsons
2010-12-30  0:46   ` Ingo Schwarze

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=4d1ac003.44842a0a.2155.4026@mx.google.com \
    --to=anthonyjbentley@gmail.com \
    --cc=discuss@mdocml.bsd.lv \
    /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).