Index: [thread] [date] [subject] [author]
  From: Wouter Scholten <wouters@cistron.nl>
  To  : ggi-develop@eskimo.com
  Date: Tue, 25 Aug 1998 19:55:32 +0200

ggi man page & info [Re: kgicon troubles]

Neal Tucker wrote:

> <rant>
> Info should be killed.  I have no idea why anyone would advocate
> such an obfuscated piece of shit as the basic access tool for
> critical information.  I'm sure it's great and very powerful once
> you know how to use it, but it's done nothing but get in my way,
> and I often find that it's the only place certain information is
> stored.  I really need to find the info2man utils that I've heard
> about.  Die, info, die.
> </rant>

use tkinfo.

However, info information is badly organised, takes ages to find what
you want (and that is WITH tkinfo, and using the search commands
heavily, so no need to remember what letter stands for what command) and
should indeed be scrapped. Even for large packages like emacs (where
info with its references is in priciple superior to man pages) it takes
#*@#% before you find what you want and you mostly don't find it at all.

Btw, the good thing about using *BSD is much less 
       This  documentation  is no longer being maintained and may
       be inaccurate or incomplete.  The Texinfo documentation is
       now the authoritative source.
BS.

Even for e.g. cp, ls you get this nonsense!

Btw 2: What abput that man page for ggi? I don't give a toss about
dvi/ps/html etc. Programmers need man pages and nothing else (for
functions at least). Therefore I suggest scrapping sgml for the libggi
doc and putting it in the man page (or pages when it gets too big for
one page). You only need to know a few commands to make man pages so
it's easy to update man pages after changing something in the API.

Wouter

Index: [thread] [date] [subject] [author]