From: schwarze@mdocml.bsd.lv
To: source@mdocml.bsd.lv
Subject: mdocml: would be nice to warn about broken .Xr links...
Date: Thu, 7 Jan 2016 20:38:02 -0500 (EST) [thread overview]
Message-ID: <16709105671046445374.enqueue@fantadrom.bsd.lv> (raw)
Log Message:
-----------
would be nice to warn about broken .Xr links...
Modified Files:
--------------
mdocml:
TODO
Revision Data
-------------
Index: TODO
===================================================================
RCS file: /home/cvs/mdocml/mdocml/TODO,v
retrieving revision 1.215
retrieving revision 1.216
diff -LTODO -LTODO -u -p -r1.215 -r1.216
--- TODO
+++ TODO
@@ -537,6 +537,11 @@ are mere guesses, and some may be wrong.
* warning issues
************************************************************************
+- provide a way in mandoc(1) to warn about broken .Xr links;
+ probably cannot be on by default in -Tlint because it needs
+ to access the manpath and mandoc.db(3) after parsing.
+ asked for by jmc@ Fri, 4 Dec 2015 22:39:40 +0000
+
- Report errors in -O suboption parsing.
loc * exist * algo * size * imp **
--
To unsubscribe send an email to source+unsubscribe@mdocml.bsd.lv
reply other threads:[~2016-01-08 1:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=16709105671046445374.enqueue@fantadrom.bsd.lv \
--to=schwarze@mdocml.bsd.lv \
--cc=source@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).