Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Chris Moller <cmoller@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFC] Do not treat '\' as escape character on MinGW Windows   hosts
Date: Thu, 22 Apr 2010 11:49:00 -0000	[thread overview]
Message-ID: <4BD037D5.8000305@redhat.com> (raw)
In-Reply-To: <20100422023421.GA20111@ednor.casa.cgf.cx>

On 04/21/10 22:34, Christopher Faylor wrote:
> On Wed, Apr 21, 2010 at 08:17:14PM -0400, Joel Brobecker wrote:
>    
>>>>         (gdb) file c:\\foo\\bar.exe
>>>>         Reading symbols from c:\foo\bar.exe...done.
>>>>          
>>> Why not just use a "forward" slash?
>>>        
>> It's not always that easy - A lot of times, the user wants to copy/paste
>> a path that's been printed by another tool.  Also, the typical Windows
>> user seems to think that he should be able to use a valid Windows path
>> (which I agree)...
>>      
>
> I agree too except when we're talking about something that is
> essentially a UNIX tool.  And, I don't see how you can talk about the
> pain of doubling up the backslashes if you're talking about cutting and
> pasting.
>
> I know I'll be outvoted here but I I hate cluttering code with MS-DOS
> workarounds.
>    

+1

> cgf
>    


  parent reply	other threads:[~2010-04-22 11:49 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
2010-04-22 11:54         ` Chris Moller
2010-04-22 12:33           ` Joel Brobecker
2010-04-22 11:49       ` Chris Moller [this message]
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=4BD037D5.8000305@redhat.com \
    --to=cmoller@redhat.com \
    --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