From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8139 invoked by alias); 22 Jun 2012 05:58:51 -0000 Received: (qmail 8127 invoked by uid 22791); 22 Jun 2012 05:58:50 -0000 X-SWARE-Spam-Status: No, hits=-3.9 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,RCVD_IN_NIX_SPAM,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout23.012.net.il (HELO mtaout23.012.net.il) (80.179.55.175) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 22 Jun 2012 05:58:20 +0000 Received: from conversion-daemon.a-mtaout23.012.net.il by a-mtaout23.012.net.il (HyperSendmail v2007.08) id <0M6000G008HB7Z00@a-mtaout23.012.net.il> for gdb-patches@sourceware.org; Fri, 22 Jun 2012 08:58:18 +0300 (IDT) Received: from HOME-C4E4A596F7 ([87.69.210.75]) by a-mtaout23.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0M6000GO78L61EA0@a-mtaout23.012.net.il>; Fri, 22 Jun 2012 08:58:18 +0300 (IDT) Date: Fri, 22 Jun 2012 05:58:00 -0000 From: Eli Zaretskii Subject: Re: [PATCH, doc]: Rename Index node to prevent file collision In-reply-to: To: Michael Hope Cc: brobecker@adacore.com, joseph@codesourcery.com, gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83a9zvdh1g.fsf@gnu.org> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 8BIT References: <4FD94EC0.1000009@linaro.org> <83ehphyhdn.fsf@gnu.org> <20120614220037.GO18729@adacore.com> <83txydf2nj.fsf@gnu.org> <83lijle3fu.fsf@gnu.org> <83ipekd496.fsf@gnu.org> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-06/txt/msg00678.txt.bz2 > From: Michael Hope > Date: Fri, 22 Jun 2012 10:36:02 +1200 > Cc: brobecker@adacore.com, joseph@codesourcery.com, gdb-patches@sourceware.org > > >> > 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 > http://sourceware.org/ml/gdb-patches/2012-06/msg00496.html. 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? OK.