From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11657 invoked by alias); 22 Apr 2010 08:17:33 -0000 Received: (qmail 11631 invoked by uid 22791); 22 Apr 2010 08:17:32 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=BAYES_00,TW_CG,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from sibelius.xs4all.nl (HELO glazunov.sibelius.xs4all.nl) (83.163.83.176) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 22 Apr 2010 08:17:27 +0000 Received: from glazunov.sibelius.xs4all.nl (kettenis@localhost [127.0.0.1]) by glazunov.sibelius.xs4all.nl (8.14.3/8.14.3) with ESMTP id o3M8H0et003942; Thu, 22 Apr 2010 10:17:01 +0200 (CEST) Received: (from kettenis@localhost) by glazunov.sibelius.xs4all.nl (8.14.3/8.14.3/Submit) id o3M8GwJP031933; Thu, 22 Apr 2010 10:16:59 +0200 (CEST) Date: Thu, 22 Apr 2010 08:17:00 -0000 Message-Id: <201004220816.o3M8GwJP031933@glazunov.sibelius.xs4all.nl> From: Mark Kettenis To: gdb-patches@sourceware.org CC: brobecker@adacore.com In-reply-to: <20100422023421.GA20111@ednor.casa.cgf.cx> (message from Christopher Faylor on Wed, 21 Apr 2010 22:34:21 -0400) Subject: Re: [RFC] Do not treat '\' as escape character on MinGW Windows hosts References: <20100421203354.GD6588@adacore.com> <20100421220828.GA19620@ednor.casa.cgf.cx> <20100422001714.GD19194@adacore.com> <20100422023421.GA20111@ednor.casa.cgf.cx> Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2010-04/txt/msg00738.txt.bz2 > Date: Wed, 21 Apr 2010 22:34:21 -0400 > From: Christopher Faylor > > 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. You're not alone.