From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: Quoting, backslashes, CLI and MI
Date: Wed, 22 Feb 2006 05:24:00 -0000 [thread overview]
Message-ID: <20060222043527.GA10442@nevyn.them.org> (raw)
In-Reply-To: <uwtfo9frt.fsf@gnu.org>
On Wed, Feb 22, 2006 at 06:30:30AM +0200, Eli Zaretskii wrote:
> > Date: Tue, 21 Feb 2006 16:33:24 -0500
> > From: Daniel Jacobowitz <drow@false.org>
> >
> > Prompted by some of Andrew's paths-with-spaces patches, and by another
> > project I'm working on that had to add a var_filename set variable,
> > I've been looking over the way GDB handles quoting of arguments.
> > It's a mess. For most users this is not a big deal; the big losers
> > are (A) pathnames with spaces in them, and (B) pathnames with backslashes in
> > them, e.g. DJGPP and MinGW32 paths.
>
> Daniel,
>
> Thanks for a comprehensive summary. I will read it in depth and
> respond by this evening; for now just one comment: the DJGPP port
> assumes the user mostly uses forward slashes, not backslashes.
> Perhaps doing that on Windows as well will make the job of fixing
> what's broken easier. I don't think it's a bad limitation.
Thanks; no rush on this - I'll find something else to keep me busy
tomorrow and be back to it.
I don't actually know which form of paths current Windows MI clients
use. I agree that it would be convenient if they mostly used forward
slashes; but it looks like Eclipse uses native backslashed paths
primarily, so I've some interest in supporting them (to perturb Eclipse
as little as possible).
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-02-22 4:35 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 [this message]
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
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=20060222043527.GA10442@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
/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