Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>
Cc: gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org
Subject: Re: [RFC] Do not treat '\' as escape character on MinGW Windows    hosts
Date: Thu, 22 Apr 2010 12:26:00 -0000	[thread overview]
Message-ID: <20100422122550.GJ19194@adacore.com> (raw)
In-Reply-To: <001601cae213$80998080$81cc8180$@muller@ics-cnrs.unistra.fr>

>   Should we rather think about a command
> that would allow to switch from Unix to Windows behavior?
> 
> set windows-escape-mode on/auto/off

Absolutely, *if* we decide that the right behavior is: preserve the
current Unixy behavior everywhere except inside the GDB interpreter.

> Of course this is only valid for GDB, I don't know
> how this could be handled within GCC.

GCC already accepts both forms, I suspect.  However, the shell from
which you are calling GCC might not. For instance, if you use a cygwin
bash to call GCC, then you cannot use c:\foo.c unless you either escape
the backslashes, or you quote your argument. But if you do it from the
CMD.exe shell, then it should work just fine.

-- 
Joel


  reply	other threads:[~2010-04-22 12:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-21 20:34 Joel Brobecker
2010-04-21 22:08 ` Christopher Faylor
2010-04-22  0:17   ` Joel Brobecker
2010-04-22  2:34     ` Christopher Faylor
2010-04-22  8:17       ` Mark Kettenis
2010-04-22 10:37       ` Joel Brobecker
2010-04-22 11:51         ` Joel Brobecker
2010-04-22 12:01           ` Pierre Muller
2010-04-22 12:26             ` Joel Brobecker [this message]
2010-04-22 11:54         ` Chris Moller
2010-04-22 12:33           ` Joel Brobecker
2010-04-22 11:49       ` Chris Moller
2010-04-22 12:47       ` André Pönitz
2010-05-05 18:49 ` Joel Brobecker
2010-05-06 23:56   ` Sergio Durigan Junior
2010-06-04 21:53     ` Tom Tromey

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=20100422122550.GJ19194@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pierre.muller@ics-cnrs.unistra.fr \
    /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