From: Ingo Schwarze <schwarze@usta.de>
To: Jan Stary <hans@stare.cz>
Cc: discuss@mdocml.bsd.lv
Subject: Re: makewhatis stuck on groffer.1
Date: Tue, 23 Apr 2019 14:01:22 +0200 [thread overview]
Message-ID: <20190423120122.GB64114@athene.usta.de> (raw)
In-Reply-To: <20190422083226.GA36008@www.stare.cz>
Hi Jan,
Jan Stary wrote on Mon, Apr 22, 2019 at 10:32:26AM +0200:
> thank you, it works now.
Thanks for testing.
> Ingo Schwarze wrote:
>> There appear to be a few more issues with that manual page that i'm
>> currently looking at.
There are at least two other issues, but both are so hard to fix
and so rare in practice that i decided to mention them in the TODO
file rather than fixing them right now, see the commit below.
> Yeah, it _is_ insane. AFAICS, it is the only manpage that defines
>
> .de author
> This file was written by
> .MTO "" "Bernd Warken" .
>
> for example, which gets rendered as
>
> AUTHOR
> This file was written by
One other case of .MTO is already mentioned in TODO:
- groff_www(7) .MTO and .URL
These macros were used by the GNU grep(1) man page.
The groff_www(7) manual page itself uses them, too.
We should probably *not* add them to mandoc.
Just mentioning this here to keep track of the abuse.
Laura Morales <lauretas at mail dot com> 20 Apr 2018 07:33:02 +0200
loc ** exist * algo * size ** imp *
But both the GNU grep(1) and groff_www(7) manual pages got fixed IIRC,
and i'm not aware of any other groff_www(7) abuse, so i don't intend
to implement .MTO and .URL.
Yours,
Ingo
--
To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv
prev parent reply other threads:[~2019-04-23 12:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-20 18:16 makewhatis stuck on groff.1 Jan Stary
2019-04-20 18:18 ` makewhatis stuck on groffer.1 Jan Stary
2019-04-20 18:21 ` Jan Stary
2019-04-21 23:03 ` Ingo Schwarze
2019-04-22 8:32 ` Jan Stary
2019-04-23 12:01 ` Ingo Schwarze [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=20190423120122.GB64114@athene.usta.de \
--to=schwarze@usta.de \
--cc=discuss@mandoc.bsd.lv \
--cc=discuss@mdocml.bsd.lv \
--cc=hans@stare.cz \
/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).