From: Baptiste Daroussin <bapt@FreeBSD.org>
To: tech@mdocml.bsd.lv
Subject: Re: Reliable way to determine that mandoc cannot render a manpage
Date: Sun, 4 Jan 2015 00:37:58 +0100 [thread overview]
Message-ID: <20150103233758.GH75600@ivaldir.etoilebsd.net> (raw)
In-Reply-To: <20150103233118.GG75600@ivaldir.etoilebsd.net>
[-- Attachment #1: Type: text/plain, Size: 747 bytes --]
On Sun, Jan 04, 2015 at 12:31:18AM +0100, Baptiste Daroussin wrote:
> Hi,
>
> On FreeBSD when switching to mandoc(1) as a default renderer for manpages I made
> it falling back on groff(1) (for now :)) if mandoc is not able to render the
> manpage
>
> To discover the bad manpages I run mandoc -Tlint -Werror and if a failure occurs
> then the fall back happens.
>
> After checking I can see that mandoc is often correctly able to render the
> manpages even if they have errors.
>
> So my question is: is there a better way to figure out automatically if mandoc
> will be able to render a manpage?
>
> Best regards
> Bapt
Nevermind -Wfatal is what I was looking for... Don't know how I missed it
Sorry for noise
Bapt
[-- Attachment #2: Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2015-01-03 23:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-03 23:31 Baptiste Daroussin
2015-01-03 23:37 ` Baptiste Daroussin [this message]
2015-01-04 14:25 ` 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=20150103233758.GH75600@ivaldir.etoilebsd.net \
--to=bapt@freebsd.org \
--cc=tech@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).