From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: $_ and info breakpoint [PATCH]
Date: Tue, 10 Jul 2007 11:20:00 -0000 [thread overview]
Message-ID: <20070710112050.GA2306@caradoc.them.org> (raw)
In-Reply-To: <u3azxaqs4.fsf@gnu.org>
On Tue, Jul 10, 2007 at 06:20:11AM +0300, Eli Zaretskii wrote:
> > Date: Mon, 9 Jul 2007 21:43:12 -0400
> > From: Daniel Jacobowitz <drow@false.org>
> > Cc: gdb-patches@sourceware.org
> >
> > On Tue, Jul 10, 2007 at 12:22:20PM +1200, Nick Roberts wrote:
> > > 2007-07-10 Nick Roberts <nickrob@snap.net.nz>
> > >
> > > * breakpoint.c: Include "top.h".
> > > (breakpoint_1): Don't set convenience variable $_ if server prefix
> > > is used.
> > > (_initialize_breakpoint): Describe this behaviour in command help.
> >
> > I didn't see your earlier suggestion, and in fact I didn't know about
> > the server command prefix at all. This seems fine to me; does anyone
> > else see a reason why we shouldn't do it?
>
> None here. I think it's a good idea.
Thanks. Nick, patch is OK for trunk; I suppose there will be a
corresponding update to the emacs mode? Or does it use 'server'
already?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-07-10 11:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <18064.7905.924535.720690@kahikatea.snap.net.nz>
[not found] ` <20070709115647.GC3095@caradoc.them.org>
2007-07-10 0:22 ` Nick Roberts
2007-07-10 1:43 ` Daniel Jacobowitz
2007-07-10 3:20 ` Eli Zaretskii
2007-07-10 11:20 ` Daniel Jacobowitz [this message]
2007-07-10 23:11 ` Nick Roberts
2007-07-10 23:51 ` Daniel Jacobowitz
2007-07-11 0:35 ` Nick Roberts
2007-07-11 11:32 ` Daniel Jacobowitz
2007-07-11 18:15 ` Jim Blandy
2007-07-11 22:56 ` $_ and info breakpoint [PATCH: doco] Nick Roberts
2007-07-12 3:19 ` 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=20070710112050.GA2306@caradoc.them.org \
--to=drow@false.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