From: "Dag-Erling Smørgrav" <des@des.no>
To: Ingo Schwarze <schwarze@usta.de>
Cc: discuss@mdocml.bsd.lv
Subject: Re: Dashes and strange markup
Date: Mon, 06 Mar 2017 17:39:55 +0100 [thread overview]
Message-ID: <86h936pdes.fsf@desk.des.no> (raw)
In-Reply-To: <20170306155714.GB58385@athene.usta.de> (Ingo Schwarze's message of "Mon, 6 Mar 2017 16:57:14 +0100")
Ingo Schwarze <schwarze@usta.de> writes:
> Well, abusing .Nd outside NAME is so bizarre that being forgiving
> about it would be a bad idea.
Technically, mandoc *is* forgiving about it: it renders it the way the
author (incorrectly) expected instead of throwing an error, which is
probably why it has gone unnoticed until now.
> Anthony correctly answered the rest, so my impression is that no
> code or documentation changes are required.
I asked for advice, not changes.
DES
--
Dag-Erling Smørgrav - des@des.no
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2017-03-06 16:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 11:17 Dag-Erling Smørgrav
2017-03-06 14:55 ` Anthony J. Bentley
2017-03-06 16:52 ` Dag-Erling Smørgrav
2017-03-06 15:57 ` Ingo Schwarze
2017-03-06 16:39 ` Dag-Erling Smørgrav [this message]
2017-03-06 17:34 ` 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=86h936pdes.fsf@desk.des.no \
--to=des@des.no \
--cc=discuss@mdocml.bsd.lv \
--cc=schwarze@usta.de \
/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).