This is the mail archive of the
gdb-patches@sourceware.cygnus.com
mailing list for the GDB project.
Re: Index in gdb.texinfo
- To: dima at Chg dot RU
- Subject: Re: Index in gdb.texinfo
- From: Eli Zaretskii <eliz at delorie dot com>
- Date: Mon, 17 Apr 2000 03:15:46 -0400 (EDT)
- CC: gdb-patches at sourceware dot cygnus dot com
- References: <200004162015.AAA39758@netserv1.chg.ru>
- Reply-to: Eli Zaretskii <eliz at is dot elta dot co dot il>
> Date: Mon, 17 Apr 2000 00:15:00 +0400 (MSD)
> From: Dmitry Sivachenko <dima@Chg.RU>
>
> > > -@kindex RET
> > > +@kindex @key{RET}
> >
> > I don't think it's a good idea to have @key in the index, it looks
> > awkward there. Isn't @code{RET} good enough for the index?
>
> We have 'complete (@key{TAB})' in Readline chapter.
I think that's wrong as well, but at least in that case, @key isn't
the first word in the entry, so it will be sorted correctly in all
formats produced by makeinfo/texi2dvi.
> By the way, what people think about splitting Index into two parts:
> Concept index and Functions and Commands index (or smth similar)?
It depends on how long the index is now. IMHO, it's not too long to
require a split (but addition of gdmi.texinfo might change that).
However, I won't mind splitting it if others think it's a good idea.