In article <1481.1207762811 at mini>,
Brad Parker <brad at heeltoe.com> writes:
So I'd offer that info pages are more than just
cumbersome poorly
hypertext'd documents. They are part of a larger system which has goals
beyond just simple man pages.
In theory I don't disagree with what info pages *could* be. In
practice though, they end up being vastly inferior to the man pages
that they replaced. A man page is best at succinctly communicating
important information about a utility: summary of usage, command-line
options supported, environment variables consumed, etc. I wouldn't
want to write a book using the an macro set for troff, but every time
I just need a quick piece of information about a command-line utility
and try to get it out of info, its a huge PITA.
Of course some things need a bona-fide full-featured cross-linked
manual -- just look at how many man pages perl sprawls across these
days.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://www.xmission.com/~legalize/book/download/index.html>
Legalize Adulthood! <http://blogs.xmission.com/legalize/>