Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [2/2] RFA: --with-system-readline -vs- gdb.texinfo
Date: Fri, 19 Nov 2010 22:14:00 -0000	[thread overview]
Message-ID: <83hbfdarps.fsf@gnu.org> (raw)
In-Reply-To: <m3lj4p9gpc.fsf@fleche.redhat.com>

> From: Tom Tromey <tromey@redhat.com>
> Date: Fri, 19 Nov 2010 13:55:11 -0700
> 
> Currently if you configure with --with-system-readline, the resulting
> gdb.info will still have its own copy of the readline manual.  This is
> the wrong thing to do -- the gdb readline might be a different version,
> so the documentation might be misleading.
> 
> This patch fixes the problem by making the uses of the included manual
> conditional on whether --with-system-readline was given.
> 
> This particular patch relies on removing gdb/doc/configure.
> If that patch does not go in, I can change this one to suit.
> 
> Tested by building both ways and looking at the appropriate nodes in the
> resulting .info file.
> 
> Please review.

OK, thanks.

>  History expansion assigns special meaning to the character @kbd{!}.
> -@xref{Event Designators}, for more details.
> +@ifset SYSTEM_READLINE
> +@xref{Using History Interactively, , , history, GNU History Library},
> +@end ifset
> +@ifclear SYSTEM_READLINE
> +@xref{Using History Interactively},
> +@end ifclear
> +for more details.

A copy/paste error?


  reply	other threads:[~2010-11-19 22:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-19 20:55 Tom Tromey
2010-11-19 22:14 ` Eli Zaretskii [this message]
2010-11-22 21:53   ` Tom Tromey
2010-11-23  3:51     ` Eli Zaretskii

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=83hbfdarps.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@redhat.com \
    /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