discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: "Ulrich Spörlein" <uqs@spoerlein.net>
To: discuss@mdocml.bsd.lv
Subject: Three small bugs?
Date: Wed, 26 May 2010 10:55:14 +0200	[thread overview]
Message-ID: <20100526085514.GF88504@acme.spoerlein.net> (raw)

Hi all,

three nits I ran into:

1. sendmail's -man pages have a header like this:

.TH MAIL.LOCAL 8 "$Date: 2003/10/20 20:26:51 $"
.SH NAME
mail.local
\- store mail in a mailbox
.SH SYNOPSIS

where groff will put the date verbatim in the footer. mandoc however
will put the current date into the footer. It would be nice if this
could be made to take the third argument to .TH literally, if parsing as
a date fails.

2. in our libthr.3 references another lib using .Lb, where trailing
punctuation makes mandoc barf.

.Sh DESCRIPTION
...
has been optimized for use by applications expecting system scope thread
semantics, and can provide significant performance improvements
compared to
.Lb libkse .
.Sh SEE ALSO
.Xr pthread 3

Please note that this .Lb call is not in the LIBRARY section.

3. Another nit is the .Ud macro, which is used a couple of times like
this:

.Sh BUGS
The
.Nm
utility is
.Ud .

where the trailing punctuation is a) not required but should b) not
break mandoc. The full stop in the source is quite handy, imho, so you
know the sentence ends here.

Which other macros "silently" end a sentence (besides Ud and Bt)?


Cheers,
Uli
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

             reply	other threads:[~2010-05-26  8:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-26  8:55 Ulrich Spörlein [this message]
2010-05-26  9:37 ` Three small bugs? (Second: Lb) Kristaps Dzonsons
2010-05-26 10:41 ` Three small bugs? (Ud handling) Kristaps Dzonsons
2010-05-26 14:13 ` Three small bugs? (TH and dates) Kristaps Dzonsons

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=20100526085514.GF88504@acme.spoerlein.net \
    --to=uqs@spoerlein.net \
    --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).