From: schwarze@mandoc.bsd.lv
To: source@mandoc.bsd.lv
Subject: mandoc: new man(1) issues from Lorenzo Beretta <loreb at github>
Date: Mon, 1 Apr 2019 10:57:59 -0500 (EST) [thread overview]
Message-ID: <e3fd133ef51d82e1@fantadrom.bsd.lv> (raw)
Log Message:
-----------
new man(1) issues from Lorenzo Beretta <loreb at github>
Modified Files:
--------------
mandoc:
TODO
Revision Data
-------------
Index: TODO
===================================================================
RCS file: /home/cvs/mandoc/mandoc/TODO,v
retrieving revision 1.289
retrieving revision 1.290
diff -LTODO -LTODO -u -p -r1.289 -r1.290
--- TODO
+++ TODO
@@ -196,6 +196,30 @@ are mere guesses, and some may be wrong.
--- missing misc features ----------------------------------------------
+- man 3am readline
+ does not work because man(1) only accepts digit + one letter,
+ otherwise explicit -s is currently required
+ https://github.com/void-linux/void-packages/issues/9868
+ loc * exist * algo * size * imp ***
+
+- man 3 readline may show readline(3m)
+ because in manpage_compare, "3" and "3am" compare equal
+ https://github.com/void-linux/void-packages/issues/9868
+ probably requires putting string version of section into struct manpage
+ loc * exist ** algo * size * imp ***
+
+- restore flags for result ordering, but only for man(1), not for apropos(1)
+ such that man 3 syslog show syslog.3 not klogctl.3
+ and such that man 3p acosl shows acosl.3p not acos.3p
+ https://github.com/void-linux/void-packages/issues/9868
+ loc * exist ** algo * size * imp ***
+
+- dead .so links should be entered into the database to avoid:
+ man -M. lvm-config
+ man: outdated mandoc.db lacks lvm-config(8) entry, run makewhatis /co/void-man
+ https://github.com/void-linux/void-packages/issues/9868
+ loc * exist ** algo * size * imp **
+
- man -ks 1,8 route; kn@ Jul 13, 2018 orally
- italic correction (\/) in PostScript mode
--
To unsubscribe send an email to source+unsubscribe@mandoc.bsd.lv
reply other threads:[~2019-04-01 15:57 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=e3fd133ef51d82e1@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).