Roland Mainz writes: > > So, why produce a poor answer when a better one is possible? > > What about the resource "manpower" ? If I take on /usr/bin/man then I > want to do a complete overhaul of that thing and not a half solution.
I don't see why fixing /usr/bin/man to do default searches in a more intelligent manner requires any other "overhaul" of the code. It looks like it may well be a fairly straightforward and independent improvement. > For example it makes me unhappy that the manual pages are in a > DocBook-like format but /usr/bin/man exposes zero features of Docbook to > the end-users (and the intermediate generation of troff files causes > trouble with tables, non-ASCII charatcers, transliteration, embedded > code examples etc.). Sure; there's plenty to be desired. I wouldn't suggest boiling away the ocean to get to it, though. I had though we were discussing the possible ways to get at the desired MANPATH=PATH behavior, not what the future may hold for man in general. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
