From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: andrew.burgess@embecosm.com, gdb-patches@sourceware.org
Subject: Re: [RFC] Use of create_new_frame from 'frame'.
Date: Wed, 08 Jul 2015 20:06:00 -0000 [thread overview]
Message-ID: <83bnfmv2hd.fsf@gnu.org> (raw)
In-Reply-To: <559D7E09.6080202@redhat.com>
> Date: Wed, 08 Jul 2015 20:46:17 +0100
> From: Pedro Alves <palves@redhat.com>
> CC: gdb-patches@sourceware.org
>
> > You could also ask the user for confirmation, when the command is
> > going to create a new frame.
>
> I'd rather the explicit approach, because querying works when
> in interactive mode, but not with scripts.
We've got the same situation with umpteen other commands, and we also
have a solution for scripts: we implicitly assume a NO answer.
But I'm not going to insist. I just wanted to remind us that there's
one more alternative.
next prev parent reply other threads:[~2015-07-08 20:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 17:09 Andrew Burgess
2015-07-08 18:02 ` Pedro Alves
2015-07-08 19:42 ` Eli Zaretskii
2015-07-08 19:46 ` Pedro Alves
2015-07-08 20:06 ` Eli Zaretskii [this message]
2015-07-08 20:16 ` Andrew Burgess
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=83bnfmv2hd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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