Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch 4/3] readline-6.2: Substitute inc-hist.texinfo
Date: Mon, 02 May 2011 16:20:00 -0000	[thread overview]
Message-ID: <20110502162014.GA28920@host1.jankratochvil.net> (raw)
In-Reply-To: <E1QGuD5-0002BT-LG@fencepost.gnu.org>

On Mon, 02 May 2011 16:34:51 +0200, Eli Zaretskii wrote:
> > --- a/readline/doc/hsuser.texi
> > +++ b/readline/doc/hsuser.texi
> > @@ -26,9 +26,10 @@ into another language, under the above conditions for modified versions.
> >  @node Using History Interactively
> >  @chapter Using History Interactively
> >  
> > -@ifclear BashFeatures
> > -@defcodeindex bt
> > -@end ifclear
> > +@c GDB bundling modification:
> > +@c @ifclear BashFeatures
> > +@c @defcodeindex bt
> > +@c @end ifclear
> 
> Why do we need to comment this out?

BTW it was already commented out the same way in readline-5.1.


> If BashFeatures is not set, the
> @defcodeindex line will not be in effect anyway.  Is something setting
> BashFeatures anywhere when we build our docs?

You are right BashFeatures is not set but this is @ifclear.  Therefore:
./../../readline/doc/hsuser.texi:31: Index `bt' already exists.


> >  This chapter describes how to use the @sc{gnu} History Library interactively,
> >  from a user's standpoint.  It should be considered a user's guide.  For
> >  information on using the @sc{gnu} History Library in your own programs,
> > -@pxref{Programming with GNU History}.
> > +@c GDB bundling modification:
> > +@pxref{Programming with GNU History, , , history, GNU History Library}.
> >  @end ifclear
> 
> Is this because the referenced node is only in the separate
> history.info manual, which is not part of hsuser.texi?

Yes:
./../../readline/doc/hsuser.texi:44: Cross reference to nonexistent node `Programming with GNU History' (perhaps incorrect sectioning?).


> If so, this is
> actually a bug in Readline docs which should be fixed upstream in a
> way that allows any project to include hsuser.texi without making such
> changes.  For example:
> 
>  @ifset HsUser
>  @pxref{Programming with GNU History, , , history, GNU History Library}.
>  @end ifset
>  @ifclear HsUser
>  @pxref{Programming with GNU History}.
>  @end ifclear
> 
> Then projects that include just hsuser.texi will need to pass the
> "-DHsUser" switch to makeinfo, while Readline will not.
> 
> I'm okay with making these changes for now, to allow people building
> GDB without failures.  But if Chet accepts the above change, we should
> switch to it in GDB, so that our doc/Makefile.in is ready for the next
> upstream release of Readline.

I guess defined BashFeatures was partially meant for some inclusion, OK.


Thanks,
Jan


  reply	other threads:[~2011-05-02 16:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-02 14:11 Jan Kratochvil
2011-05-02 14:35 ` Eli Zaretskii
2011-05-02 16:20   ` Jan Kratochvil [this message]
2011-05-02 17:06     ` Eli Zaretskii
2011-05-02 17:11       ` Jan Kratochvil

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110502162014.GA28920@host1.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox