From: Daniel Jacobowitz <drow@false.org>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: Jim Blandy <jimb@red-bean.com>, gdb@sourceware.org
Subject: Re: Quoting, backslashes, CLI and MI
Date: Wed, 22 Feb 2006 19:28:00 -0000 [thread overview]
Message-ID: <20060222192348.GA30642@nevyn.them.org> (raw)
In-Reply-To: <43FCB929.2060808@st.com>
On Wed, Feb 22, 2006 at 07:19:05PM +0000, Andrew STUBBS wrote:
> Daniel Jacobowitz wrote:
> >Then there's the question of what to do with CLI "set args". People
> >use this today and it is passed literally to the program, without any
> >interpretation of quotes or escapes - if you want that to happen you
> >wait for the shell to do it. I don't think that we can really change
> >that - we can bump the interface version on MI, but we can't really
> >bump it on our CLI users' fingers :-)
>
> remote-sim.c already uses build_argv for its args.
I think that the number of people who pass complicated args to programs
run on the simulator is probably much smaller than the number who do so
to programs run natively; fork-child.c will trump in this case. For
instance, local system filenames.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-02-22 19:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 4:30 Daniel Jacobowitz
2006-02-22 4:35 ` Paul Koning
2006-02-22 19:57 ` Daniel Jacobowitz
2006-02-22 21:57 ` Paul Koning
2006-02-23 4:25 ` Mark Kettenis
2006-02-25 1:30 ` Eli Zaretskii
2006-02-22 4:40 ` Eli Zaretskii
2006-02-22 5:24 ` Daniel Jacobowitz
2006-02-22 19:30 ` Eli Zaretskii
2006-02-22 20:59 ` Daniel Jacobowitz
2006-02-22 17:39 ` Jim Blandy
2006-02-22 18:01 ` Daniel Jacobowitz
2006-02-22 18:05 ` Jim Blandy
2006-02-22 18:11 ` Daniel Jacobowitz
2006-02-22 19:24 ` Andrew STUBBS
2006-02-22 19:28 ` Daniel Jacobowitz [this message]
2006-02-22 19:50 ` Eli Zaretskii
2006-02-22 19:34 ` Eli Zaretskii
2006-02-22 19:53 ` Daniel Jacobowitz
2006-02-23 11:13 ` Eli Zaretskii
2006-02-22 19:25 ` Eli Zaretskii
2006-02-22 19:51 ` Daniel Jacobowitz
2006-02-23 4:32 ` Eli Zaretskii
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=20060222192348.GA30642@nevyn.them.org \
--to=drow@false.org \
--cc=andrew.stubbs@st.com \
--cc=gdb@sourceware.org \
--cc=jimb@red-bean.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