From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24334 invoked by alias); 2 Jul 2012 01:03:32 -0000 Received: (qmail 24298 invoked by uid 22791); 2 Jul 2012 01:03:30 -0000 X-SWARE-Spam-Status: No, hits=-3.1 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from mail-wg0-f43.google.com (HELO mail-wg0-f43.google.com) (74.125.82.43) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 02 Jul 2012 01:03:17 +0000 Received: by wgbdr1 with SMTP id dr1so3666210wgb.12 for ; Sun, 01 Jul 2012 18:03:16 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=WVS4d64FD0JzW23wGZUeL0hMjNrHwLHPDBOkigxyvBs=; b=VGj8FJJwobAZT1eWsDbs/oEI/6raHo7rkubHE99/aopgSYf1T/c5+TMJLbtxBjJLvU tf8MA6fd44ssIV5Ssz4J1kzBuTx1vIh/omP1NoPstiB8jPL1+NmOtJ3fAHLM3PY3LjUc /yPG29o4uO+4OpKeTUpFUEXagRmr1OyHQZ09+XiLPz4pYXr5we6i/B5woyBof+LzUuZB 0xECq4KnZWzrgTjbh75VLwuUWS7vPRnhbU1kcrMRyBiNSTGKlCknhvXzda7VHY8nCQXF icc+n5njdHXspKtMovdlQNuNskUjYyl20U65MmB46m5A1tcfc8vXIWMy/IRSmyBn1Lg5 3b0A== Received: by 10.216.131.104 with SMTP id l82mr821356wei.218.1341190996385; Sun, 01 Jul 2012 18:03:16 -0700 (PDT) MIME-Version: 1.0 Received: by 10.180.83.170 with HTTP; Sun, 1 Jul 2012 18:02:56 -0700 (PDT) In-Reply-To: <83r4sv5k9h.fsf@gnu.org> 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> <83a9zvdh1g.fsf@gnu.org> <837guzd5q1.fsf@gnu.org> <83r4sv5k9h.fsf@gnu.org> From: Michael Hope Date: Mon, 02 Jul 2012 01:03:00 -0000 Message-ID: Subject: Re: [PATCH, doc]: Rename Index node to prevent file collision To: Eli Zaretskii Cc: brobecker@adacore.com, joseph@codesourcery.com, gdb-patches@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQlkPGN+QenBU81W82mZ6MEpjpAvIGt1BppfckpqxIbjYcBWX6awvxGQpmZhG+eGbF3L07Hp 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-07/txt/msg00004.txt.bz2 On 2 July 2012 07:55, Eli Zaretskii wrote: > Ping! Should I commit this? It fixes my issue, -- Michael >> Date: Fri, 22 Jun 2012 13:02:46 +0300 >> From: Eli Zaretskii >> Cc: brobecker@adacore.com, joseph@codesourcery.com, gdb-patches@sourceware.org >> >> > Date: Fri, 22 Jun 2012 08:58:19 +0300 >> > From: Eli Zaretskii >> > Cc: brobecker@adacore.com, joseph@codesourcery.com, gdb-patches@sourceware.org >> > >> > > >> > 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. >> >> Here it is. Does this solve your problem? >> >> >> Index: gdb.texinfo >> =================================================================== >> RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v >> retrieving revision 1.978 >> diff -u -p -r1.978 gdb.texinfo >> --- gdb.texinfo 22 Jun 2012 08:37:49 -0000 1.978 >> +++ gdb.texinfo 22 Jun 2012 10:01:35 -0000 >> @@ -18,13 +18,17 @@ >> @end iftex >> >> @finalout >> -@syncodeindex ky cp >> -@syncodeindex tp cp >> +@c To avoid file-name clashes between index.html and Index.html, when >> +@c the manual is produced on a Posix host and then moved to a >> +@c case-insensitive filesystem (e.g., MS-Windows), we separate the >> +@c indices into two: Concept Index and all the rest. >> +@syncodeindex ky fn >> +@syncodeindex tp fn >> >> @c readline appendices use @vindex, @findex and @ftable, >> @c annotate.texi and gdbmi use @findex. >> -@syncodeindex vr cp >> -@syncodeindex fn cp >> +@syncodeindex vr fn >> +@syncodeindex fn fn >> >> @c !!set GDB manual's edition---not the same as GDB version! >> @c This is updated by GNU Press. >> @@ -182,7 +186,9 @@ software in general. We will miss him. >> * Copying:: GNU General Public License says >> how you can copy and share GDB >> * GNU Free Documentation License:: The license for this documentation >> -* Index:: Index >> +* Concept Index:: Index of @value{GDBN} concepts >> +* Command and Variable Index:: Index of @value{GDBN} commands, variables, >> + functions, and Python data types >> @end menu >> >> @end ifnottex >> @@ -1780,8 +1786,9 @@ In addition to @code{help}, you can use >> and @code{show} to inquire about the state of your program, or the state >> of @value{GDBN} itself. Each command supports many topics of inquiry; this >> manual introduces each of them in the appropriate context. The listings >> -under @code{info} and under @code{show} in the Index point to >> -all the sub-commands. @xref{Index}. >> +under @code{info} and under @code{show} in the Command, Variable, and >> +Function Index point to all the sub-commands. @xref{Command and Variable >> +Index}. >> >> @c @group >> @table @code >> @@ -40415,11 +40422,16 @@ A string in the constant pool is zero-te >> @appendix GNU Free Documentation License >> @include fdl.texi >> >> -@node Index >> -@unnumbered Index >> +@node Concept Index >> +@unnumbered Concept Index >> >> @printindex cp >> >> +@node Command and Variable Index >> +@unnumbered Command, Variable, and Function Index >> + >> +@printindex fn >> + >> @tex >> % I think something like @@colophon should be in texinfo. In the >> % meantime: >>