From: Eli Zaretskii <eliz@gnu.org>
To: gdb@sourceware.org
Subject: Re: Quoting, backslashes, CLI and MI
Date: Wed, 22 Feb 2006 19:30:00 -0000 [thread overview]
Message-ID: <uek1vkxid.fsf@gnu.org> (raw)
In-Reply-To: <20060222043527.GA10442@nevyn.them.org> (message from Daniel Jacobowitz on Tue, 21 Feb 2006 23:35:27 -0500)
> Date: Tue, 21 Feb 2006 23:35:27 -0500
> From: Daniel Jacobowitz <drow@false.org>
>
> 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).
If we want to support backslashes on Windows _and_ backslash-escaping
without lots of ugly system-dependent code, then we will have to
require to double each backslash. Which I think will be inconvenient.
next prev parent reply other threads:[~2006-02-22 19:25 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 [this message]
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=uek1vkxid.fsf@gnu.org \
--to=eliz@gnu.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