Re: Emacs cvs newbie problems

[karl@freefriends.org (Karl Berry)]

    How about changing makeinfo to complain when the specified dircategory
    is not among the few standard ones ?

I think that would be too frustrating -- the problem is that there is
more than a few.  I wouldn't want to prejudge a maintainer's decision on
what category to use.

    I suggest we change `Linux' to `GNU/Linux' 

Yes.  Actually I just removed that category some time ago.

    and change `GNU Emacs Lisp'
    to `GNU Emacs' (or maybe `Emacs' which is what Emacs uses).

Well, my thought was that the main `Emacs' entry could be in `GNU
packages', and then all the manuals for the elisp addons would be `GNU
Emacs Lisp'.  Then the main emacs entry is not lost in the welter of
other emacs-related entries.  But I'm certainly not going to insist,
whatever you think best.

     Also I don't understand the difference between
    `GNU programming tools' and `GNU programming documentation'.

GNU packages: programs that any user might use
GNU programming tools: programs that only programmers use
GNU programming documentation: related documentation for programmers

As in:

GNU programming documentation
* GDB internals: (gdbint).      Debugger internals.
* Ld internals: (ldint).        GNU linker internals.
* Source config: (cfg-paper).   Some theory on configuring source packages.
* Stabs: (stabs).               Symbol table debugging information format.

GNU programming tools
* As: (as).                     Assembler.
* Autoconf: (autoconf).         Create source code configuration scripts
* Binutils: (binutils).         ar/copy/objdump/nm/size/strip/ranlib.
* Bison: (bison).               LALR(1) parser generator.
* CVS: (cvs).                   Concurrent versions system for source control.
* Cpp: (cpp).		        The GNU C preprocessor.
...

I'll see if I can come up with some more concrete recommendations and
put them in the manual.