From: Hui Zhu <teawater@gmail.com>
To: Marc Khouzam <marc.khouzam@ericsson.com>
Cc: "tromey@redhat.com" <tromey@redhat.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: How to set default value of yquery and nquery
Date: Thu, 25 Feb 2010 16:26:00 -0000 [thread overview]
Message-ID: <daef60381002242234l59f1f0f4g8a8ae43f1021d57d@mail.gmail.com> (raw)
In-Reply-To: <F7CE05678329534C957159168FA70DEC5243F34D05@EUSAACMS0703.eamcs.ericsson.se>
On Wed, Feb 24, 2010 at 21:42, Marc Khouzam <marc.khouzam@ericsson.com> wrote:
>
>> Do you think we can add a command to set the non-terminal
>> query answer?
>> For example:
>> set non-terminal-query-default yes/no/auto
>> auto This is the default value. query/yquery/nquery answer
>> will like before.
>> yes query/yquery/nquery answer will be yes
>> no query/yquery/nquery answer will be no
>
> This is not perfect because every query would be answered
> the same way. From a non-terminal, you many want to answer
> 'y' to one query and 'n' to another.
>
For my idea, it just to handle the query/yquery/nquery and simple commands.
After this command complete, set it back to auto can handle it.
>
> Furthermore, sometimes the query is not directly triggered
> by the command used. For example, changing a variable value
> will trigger a query from PRecord, but it is not really
> the 'set' command that sends the query, it is PRecord.
>
Sorry for make you spend a lot of time on query and prec, I think
yquery and nquery didn't can be control when non-terminal is really a
big trouble.
I will try to make each of them have a set commands. And could you
tell me which one make you feel bad? I will do it first. :)
> I believe the cleanest solution up to now was to have
> individual setting for each query. I didn't like that too much
> myself, but I don't have a better suggestion.
>
I suggest each nquery or yquery have a set command together.
The more clear way I think is the query will tell user howto set it
non-terminal. Maybe it is too tangled.
Best regards,
Hui
next prev parent reply other threads:[~2010-02-25 6:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 7:08 Hui Zhu
2010-02-23 7:53 ` MI Interface and Pretty Print to_string() result Elmenthaler, Jens
2010-03-03 22:14 ` Tom Tromey
2010-03-04 8:14 ` Elmenthaler, Jens
2010-03-05 23:49 ` Tom Tromey
2010-03-07 10:16 ` Elmenthaler, Jens
2010-03-08 20:17 ` Tom Tromey
2010-02-23 17:13 ` How to set default value of yquery and nquery Tom Tromey
2010-02-24 6:08 ` Marc Khouzam
2010-02-24 9:53 ` Hui Zhu
2010-02-24 16:41 ` Marc Khouzam
2010-02-25 16:26 ` Hui Zhu [this message]
2010-02-26 0:23 ` Marc Khouzam
2010-02-26 17:31 ` Hui Zhu
2010-02-24 6:19 ` Hui Zhu
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=daef60381002242234l59f1f0f4g8a8ae43f1021d57d@mail.gmail.com \
--to=teawater@gmail.com \
--cc=gdb@sourceware.org \
--cc=marc.khouzam@ericsson.com \
--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