In man(1) mode with a specific section requested,

try harder to find the best match.

Use this order of preference:
1. The section in both the directory name and the file name matches exactly.
2. The section in the file name matches exactly.
3. The section in the directory name matches exactly.
4. Neither of them matches exactly.
The latter can happen when mansearch() finds substring matches
or when the second .Dt argument mismatches the dir and file names.

Lorenzo Beretta <loreb at github> reported that this caused real
problems on Void Linux, like "man 3 readline" showing readline(3m).
See https://github.com/void-linux/void-packages/issues/9868 for details.

1 files changed, 0 insertions, 12 deletions

diff --git a/TODO b/TODO
index b45986eb..cdf256e1 100644
--- a/TODO
+++ b/TODO
@@ -217,18 +217,6 @@ 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 ***
-
 - 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