From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18889 invoked by alias); 22 Feb 2006 19:53:12 -0000 Received: (qmail 18881 invoked by uid 22791); 22 Feb 2006 19:53:11 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Wed, 22 Feb 2006 19:53:09 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1FC02s-0008Ac-W7; Wed, 22 Feb 2006 14:53:07 -0500 Date: Wed, 22 Feb 2006 20:59:00 -0000 From: Daniel Jacobowitz To: Eli Zaretskii Cc: gdb@sourceware.org Subject: Re: Quoting, backslashes, CLI and MI Message-ID: <20060222195306.GB31315@nevyn.them.org> Mail-Followup-To: Eli Zaretskii , gdb@sourceware.org References: <20060221213324.GA30729@nevyn.them.org> <20060222043527.GA10442@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-02/txt/msg00309.txt.bz2 On Wed, Feb 22, 2006 at 09:24:10PM +0200, Eli Zaretskii wrote: > > Date: Tue, 21 Feb 2006 23:35:27 -0500 > > From: Daniel Jacobowitz > > > > 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. For the CLI, yes, this is somewhat inconvenient. I think the consistency benefits trump that; the user can always enter forward slashes instead. And we already need to double backslashes in some places (like "file"). For the MI, it's not at all inconvenient; e.g. Eclipse already has code to do this in most places (though as I mentioned, it's not quite correct). -- Daniel Jacobowitz CodeSourcery