From: "Doug Evans" <dje@google.com>
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: "Andrew STUBBS" <andrew.stubbs@st.com>,
msnyder@specifix.com, drow@false.org, schwab@suse.de,
gdb@sources.redhat.com
Subject: Re: Strangeness in set command
Date: Wed, 09 Apr 2008 00:35:00 -0000 [thread overview]
Message-ID: <e394668d0804081337p68396783r54caf97fbb3d7edf@mail.gmail.com> (raw)
In-Reply-To: <ubq4kb2fl.fsf@gnu.org>
On Tue, Apr 8, 2008 at 11:56 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Andrew STUBBS <andrew.stubbs@st.com>
> > Eli Zaretskii wrote:
> > > 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
>
> That one could be special-cased.
There's also prompt, env, and others. Maybe the thing to do is key
off of var_string, etc., except that one can pass expressions for
integer/boolean vars. Does the command parser know in time what it's
working with?
next prev parent reply other threads:[~2008-04-08 20:38 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
2008-04-08 20:45 ` Eli Zaretskii
2008-04-09 0:35 ` Doug Evans [this message]
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=e394668d0804081337p68396783r54caf97fbb3d7edf@mail.gmail.com \
--to=dje@google.com \
--cc=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