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



> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Joel Brobecker
> Envoyé : Thursday, April 22, 2010 1:52 PM
> À : gcc-patches@gcc.gnu.org
> Cc : gdb-patches@sourceware.org
> Objet : Re: [RFC] Do not treat '\' as escape character on MinGW Windows
> hosts
> 
> Ooops - I had intended to start this email thread on GCC-patches,
> Cc'ing GDB-patches, but I made a typo, and sent it to GDB-patches
> Cc'ing the very same GDB-patches. I hope you'll forgive the cross post,
> but since this is common code...
> 
> Here is what has been discussed, so far... I'm mostly trying to discuss
> the idea of making backslash a normal character as opposed to an escape
> character in arguments when on (MinGW) windows, whether the idea gets
> sufficiently positive feedback that we can move ahead an implement this
> suggestion (patch attached FYI).

  Should we rather think about a command
that would allow to switch from Unix to Windows behavior?

set windows-escape-mode on/auto/off

The default 'auto' mode
would adapt to the target we are debugging
which would be 'on' for mingw* targets and possibly other Windows-like
targets
and 'off' for most others (this would become a gdbarch or a tdep field...).

  People that really dislike this could still
force old behavior by setting
'set windows-escape-mode' to 'off'.

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


Pierre Muller
Pascal language support maintainer for GDB






  reply	other threads:[~2010-04-22 12:01 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 [this message]
2010-04-22 12:26             ` Joel Brobecker
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='001601cae213$80998080$81cc8180$@muller@ics-cnrs.unistra.fr' \
    --to=pierre.muller@ics-cnrs.unistra.fr \
    --cc=brobecker@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@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