From: schwarze@mandoc.bsd.lv
To: source@mandoc.bsd.lv
Subject: mandoc: error message for invalid -S argument
Date: Fri, 10 Aug 2018 17:43:50 -0500 (EST) [thread overview]
Message-ID: <c89ef11862db08cd@fantadrom.bsd.lv> (raw)
Log Message:
-----------
error message for invalid -S argument
Modified Files:
--------------
mandoc:
TODO
Revision Data
-------------
Index: TODO
===================================================================
RCS file: /home/cvs/mandoc/mandoc/TODO,v
retrieving revision 1.261
retrieving revision 1.262
diff -LTODO -LTODO -u -p -r1.261 -r1.262
--- TODO
+++ TODO
@@ -523,6 +523,15 @@ are mere guesses, and some may be wrong.
* warning issues
************************************************************************
+- When a man(1) command returns no result and there was an -S
+ argument, check the -S argument against the list of valid
+ architectures and say "Unknown architecture AAA" rather than
+ "No entry for NNN in the manual" if there is no match.
+ Requires moving the lists of valid architectures out of
+ mdoc_validate.c such that they can be used by main.c.
+ Discussed with jmc@ 10 Aug 2018 19:20:12 +0100.
+ loc ** exist * algo * size * imp **
+
- warn about duplicate .Sh/.Ss heads
gre(4): Rename duplicate sections 20 Apr 2018 15:27:33 +0200
loc * exist * algo * size * imp **
--
To unsubscribe send an email to source+unsubscribe@mandoc.bsd.lv
reply other threads:[~2018-08-10 22:43 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=c89ef11862db08cd@fantadrom.bsd.lv \
--to=schwarze@mandoc.bsd.lv \
--cc=source@mandoc.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).