| ▲ | tengwar2 4 hours ago | |||||||
And I said that the man pages would be a part of what you have to examine. 95 pages in the case of bash (that's after running it through troff). man pages were fine when they were three pages long, but their lack of any internal index has become a problem. Ok, now you might have a dozen files which could contain the information, where the location of each file can be modified by environment variables. It's tolerable if you are working on something you change weekly, but a practical problem if you do it yearly or it's entirely new. | ||||||||
| ▲ | BenjiWiebe 2 hours ago | parent [-] | |||||||
'man bash'. Type G. Press PgUp until you see the FILES heading (took one press for my terminal size). There's your list of files. Alternatively, instead of G and PgUp, type /FILES<Enter>. Of course, this doesn't help at all when software either doesn't have manpages, or doesn't include the list of files in the manpage. Just nitpicking your bash example. | ||||||||
| ||||||||