🚀 go-pugleaf

Summary: There is no easy way to proofread info files.
	This makes it difficult to produce texinfo documentation.

The main problem is that it is hard to add temporarily a new info file
to the info tree if you don't have write access to the top-level info
directory.  To read a new file in info, I have to specify its full name.
If I am editing a texinfo file, there is no way to tell info to reread
the file when I change it, which means I have to kill info (or at least
switch to a different file) and specifiy the file again ... and again
and again and again...

* makeinfo program is undocumented.  There should be an entry in the
texinfo docs at least.  Maybe "makeinfo" has options specifying useful
things, but how can I find out?

* The "info" program itself is undocumented (there is no info or man
page for it; what sort of an advertisement for info is this supposed to
be?).  Grepping the source I find it has an undocumented INFOPATH
variable.  Groovy.  This still doesnt quite address the problem of
specifying THIS FILE HERE tho.

* Xinfo is undocumented.  It has no INFOPATH so far as I can tell but
"strings" tells me that it probably has a resource called "infoPath".
Wonderful.  Now I have to make sure I keep two bits of customization --
in completely different files -- up to date in parallel.  (Maybe Emacs's
info mode also has an info-path.  Who can tell?)  I wonder what format
this undocumented resource is supposed to be in.  Too bad "info",
"Xinfo" and Emacs info-mode can't all use INFOPATH (overriding an X
resource or lisp variable respectively).

* Xinfo doesn't understand tilde in file names -- so I have to use my
full directory name each time I try to read a file.

* The slot for entering node names in on the Xinfo panel does not resize
and has no scrollbar -- so typing long node names has to be done blind!
(And if I am hacking an info file in /users/me/somedir/somepackage then
the node name is pretty long.)  If I press RET in the little window,
Xinfo usually dies with a segmentation fault.

* A few quibbles: The info documentation does not state that nodes must
begin with

        NEWLINE ^_ [ ^L ] NEWLINE

I tried making an info file starting with "^_" and all the info-reading
programs could not find the first node.  Very frustrating.

The info documentation assumes you are reading in Emacs's info-mode and
can see the "Node: foo" line at the top of the screen.  In Xinfo this
information is replaced by the button labels.  The info info node should
give an example node head line or something.

texinfo.tex gives ENORMOUS values to \parskip.  Why?