🚀 go-pugleaf

In article <9104191301.AA03676@apple-gunkies.gnu.ai.mit.edu> rms writes:
>I don't think it's advisable for people to write INfo files directly,
>and for that reason I think that the work being done on making this
>easier is misdirected.
>
>Why not write Info files directly?  Because, by writing a Texinfo file
>instead, you can make a printed manual as well as an Info file.  It's
>very useful for all GNU documentation to be printable as well as
>browsable; probably that is true for your documentation projects as
>well.

The Info tree, which allows tree structured access to information as
well as cross references, can be used as a simple information keeping
system.   You can classify information however you like and add cross
references whereever you like.  It's not as good as a hypertext system
could be, but it's a lot better than a Rolodex.  It also works now.

However, there would be no reason to print such a file out; at least,
there would be no reason to have it look like a manual.  So there are
uses for Info files that are created and edited online.
-- 
Ian Taylor                   ian@airs.com                  uunet!airs!ian
First person to identify this quote wins a free e-mail message:
``But this machine chews all kinds of paper into a thick porridge that no
  chemist in the world, however skilled a criminal he may be, can read.''