This is the mail archive of the mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH, doc]: Rename Index node to prevent file collision

> From: Michael Hope <>
> Date: Fri, 22 Jun 2012 10:36:02 +1200
> Cc:,,
> >> > I fail to understand why working around by changes in one file
> >> > (gdb.texinfo) is acceptable, but working around in another file
> >> > (makeinfo's source) is not. ?I guess I'm missing something.
> >>
> >> GDB is an active project. ?Even if makeinfo was alive, it's nice to be
> >> able to use the tools already shipped with long term releases like
> >> Ubuntu 10.04.
> >
> > Texinfo is actively maintained as well.
> The last release was four years ago.  The list has around five threads
> a month.  The ChangeLog shows recent development by Karl.

I don't see how this matters, when you have a publicly accessible CVS
repository.  What's important is that there are 3 active developers
who are responsive to questions and bug reports.

> I'm happy to post a patch to makeinfo similar to
>  I'll do
> that next as another avenue.

Thank you.

> >> > The problem with your suggestion is that the GDB index is not a
> >> > concept index, it is all the indices lumped into one. ?But I would be
> >> > OK if we separate the concept index from the rest, and then we could
> >> > have "Concept Index" and "Command and Variable Index".
> >>
> >> I'd rather not go there as it's a big change for little gain.
> >
> > ??? It's as simple as modifying the "@syncodeindex" directives at the
> > beginning of gdb.texinfo, and then adding 2 @node lines for the two
> > indices, instead of the current one. ?All the rest will be done by
> > makeinfo. ?Am I missing something?
> Sorry, I assumed that we'd have to check and perhaps update each index
> entry to see that it's in the right category.

No.  We already have separate index categories: see the @kindex,
@findex, @vindex, etc. directives, in addition to @cindex, that we
have all over the manual.  It's just that these 4 directives at the
beginning of gdb.texinfo:

  @syncodeindex ky cp
  @syncodeindex tp cp

  @c readline appendices use @vindex, @findex and @ftable,
  @c annotate.texi and gdbmi use @findex.
  @syncodeindex vr cp
  @syncodeindex fn cp

arrange for all of them to be lumped into a single index "cp" (which
stands for "Concept Index"), and so this directive in the single
"Index" node we have:

  @printindex cp

prints all of the index entries together.

> Your texinfo foo is better than mine - could you post a patch?


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]