From: Andrew STUBBS <andrew.stubbs@st.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Michael Snyder <msnyder@specifix.com>,
drow@false.org, schwab@suse.de, gdb@sources.redhat.com
Subject: Re: Strangeness in set command
Date: Tue, 08 Apr 2008 20:38:00 -0000 [thread overview]
Message-ID: <47FB4FAA.9000107@st.com> (raw)
In-Reply-To: <ulk3pbh2f.fsf@gnu.org>
Eli Zaretskii wrote:
>> From: Michael Snyder <msnyder@specifix.com>
>> Cc: Eli Zaretskii <eliz@gnu.org>, Andreas Schwab <schwab@suse.de>, gdb@sources.redhat.com
>> Date: Mon, 07 Apr 2008 12:05:59 -0700
>>
>> The problem is that "so long as it is not ambiguous"
>> is dicy, and changes over time as we add new subcommands
>> to "set".
>>
>> The shortcut is probably one of those "seemed like a
>> good idea at the time" things, but now it's established
>> and we're stuck with it.
>>
>> It would probably be a good idea if, every time we parse
>> a "set" command, we try to match it with BOTH a variable
>> AND a subcommand, and if there is ambiguity we say so
>> explicitly.
>
> Or maybe, if the text after "set " has a `=' character in it, we
> should ask whether the user really meant "set variable". IOW, refuse
> to obey this shortcut, even if it's unambiguous.
>
Hmmm, that's not great for set args:
(gdb) set args --command=myscript
next prev parent reply other threads:[~2008-04-08 10:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-05 16:49 Eli Zaretskii
2008-04-05 16:56 ` Andreas Schwab
2008-04-05 18:54 ` Eli Zaretskii
2008-04-07 8:47 ` Daniel Jacobowitz
2008-04-07 18:32 ` Andrew STUBBS
2008-04-07 19:28 ` Michael Snyder
2008-04-07 19:37 ` Eli Zaretskii
2008-04-08 20:38 ` Andrew STUBBS [this message]
2008-04-08 20:45 ` Eli Zaretskii
2008-04-09 0:35 ` Doug Evans
2008-04-09 0:44 ` Michael Snyder
2008-04-09 17:24 ` Tom Tromey
2008-04-09 17:36 ` Michael Snyder
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=47FB4FAA.9000107@st.com \
--to=andrew.stubbs@st.com \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=msnyder@specifix.com \
--cc=schwab@suse.de \
/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