From: Doug Evans <dje@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [2/2] RFA: implement 'set print symbol'
Date: Tue, 17 Apr 2012 00:54:00 -0000 [thread overview]
Message-ID: <CADPb22S=6CEtoAxXLa2=C-vV6ZVVmftS4zsB73XSEujR32SmqA@mail.gmail.com> (raw)
In-Reply-To: <83aa2k6n96.fsf@gnu.org>
On Tue, Apr 10, 2012 at 12:48 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Tue, 10 Apr 2012 08:52:26 +0200
>> From: Jan Kratochvil <jan.kratochvil@redhat.com>
>> Cc: Tom Tromey <tromey@redhat.com>, gdb-patches@sourceware.org
>>
>> On Tue, 10 Apr 2012 08:15:20 +0200, Eli Zaretskii wrote:
>> > I'm confused. What is the plan now?
>>
>> Everything the same, just by default it will be now "set print symbol on".
>> But one can manually "set print symbol off" to retain the GDB-7.4 behavior.
>
> Why do we need to retain the old behavior? You yourself said that no
> one will find this option to use it. My vote is to have the new
> behavior as the only one. The mess with "set print" and p/a is
> already too much, even without an additional knob.
>
> But if we must have it, I would suggest to call it "set print
> no-symbol", and have it off by default. (Yes, I know: double negation
> is not an ideal situation, but it is IMO better than the aggravation
> from the need to type more to disambiguate the command for
> completion.)
Hi.
Yeah, double-negation is, umm, nasty.
Let's pick something non-double-negative. It can't be that hard.
next prev parent reply other threads:[~2012-04-17 0:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 18:03 Tom Tromey
2012-04-05 21:13 ` Eli Zaretskii
2012-04-09 14:32 ` Tom Tromey
2012-04-09 16:31 ` Eli Zaretskii
2012-04-09 17:44 ` Tom Tromey
2012-04-09 17:55 ` Eli Zaretskii
2012-04-09 18:00 ` Tom Tromey
2012-04-09 19:14 ` Jan Kratochvil
2012-04-09 19:21 ` Tom Tromey
2012-04-09 19:36 ` Jan Kratochvil
2012-04-09 20:45 ` Eli Zaretskii
2012-04-09 21:04 ` Tom Tromey
2012-04-10 6:17 ` Eli Zaretskii
2012-04-10 6:56 ` Jan Kratochvil
2012-04-10 7:50 ` Eli Zaretskii
2012-04-10 8:19 ` Jan Kratochvil
2012-04-16 21:14 ` Tom Tromey
2012-05-14 19:39 ` Tom Tromey
2012-04-17 0:54 ` Doug Evans [this message]
2012-04-17 11:43 ` Tom Tromey
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='CADPb22S=6CEtoAxXLa2=C-vV6ZVVmftS4zsB73XSEujR32SmqA@mail.gmail.com' \
--to=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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