Control: tag -1 fixed-upstream On Thu, Jun 01, 2017 at 11:48:38PM +0000, Bjarni Ingi Gislason wrote: > about the output of "man -d -l <file>". > > The location of the <file> is already known. > > There are so many irrelevant lines about where the location of the input > file could be, that it makes it more difficult and time consuming to spot > relevant lines.
Most of this is from parsing the configuration file. man still has to do this and determine the manpath even in the -l case, and it's not irrelevant. While it's true that the location of the manual page is *usually* known, that isn't always so: if you give "man -l" a full path to an executable then it will try to look up the executable's name in the appropriate parts of the manpath on the basis that that's more likely to be helpful than spewing binary data all over your screen; and of course we also need things like pager configuration that may be set in the configuration file. That said, it's certainly true that the debugging output was less tight than it could have been: I want to keep enough in there to allow me to still be able to diagnose users' problems effectively, but it could be rather less redundant. I've pushed a couple of commits upstream that make it substantially shorter and less noisy: https://git.savannah.gnu.org/cgit/man-db.git/commit/?id=84b6f4457e5ee1c6372ca60c303ad9c71b5f6d27 https://git.savannah.gnu.org/cgit/man-db.git/commit/?id=6580d8cd2e72ac6df1f0bb6f6876e80bca9fded3 Thanks, -- Colin Watson [cjwat...@debian.org]
