🚀 go-pugleaf

In article <kv13neINN4e9@almaak.usc.edu> ajayshah@almaak.usc.edu (Ajay Shah) writes:
>lm@slovax.Eng.Sun.COM (Larry McVoy) writes:
>
>>mib@geech.gnu.ai.mit.edu (Michael I Bushnell) writes:
>>: 
>>: The GNU manuals will be in texinfo format, with a
>>: conversion/installation program for adding tmac.an format manuals.

GOOD.

>I have seen Unix manuals produced using troff and IMHO Tex(info)
>produces far better quality.
>
>- Knuth has done great work on fonts,

So has Adobe.  I can print man pages in a number of pleasing fonts.  This
isn't especially -man dependant.  I guess it's a matter of taste.

>- Support for toc, indexes, cross-referencing, etc. is excellent,

Feature.  Would that man did.

>- You get something which looks like a book and not like a man page

Sometimes I want something that looks like a man page -- concise and to
the point (not that all man pages are, but that's a limitation inherent in
writers, not man pages or info).

>- You get a "hypertext" online manual "for free".  ``All'' we need is
>  a standalone info program and a little glue code and we can say
>  things like
>                info sort
>  to get the sort man page (just like man sort), with the value added of
>  being hypertext.

Feature.

>I started reading the Texinfo manual last night and I quite like what
>I see.  (I'm biased, being a LaTeX/TeX user already).

But I'm not.  Working in a relatively complex environment (UNIX), I don't
want to learn anything new unless it's an improvement.

Is it?  So far, I'm rather ambivalent.  I like the idea of hypertext, but
Info has more overhead, and if I wanted a sophisticated reference system,
I'd pick up the book and hope it had a good index.  And I have yet to find
a way (either info or emacs-info) to globally search for strings, which
upon occasion I want to do.  In fact, I've found emacs manual-entry most
useful to this end.

Actually, emacs-info/emacs manual-entry are my favorites.  Raw info is kind
of, well, raw.  I don't like the pager.

Michael