From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1938 invoked by alias); 22 Feb 2006 19:23:19 -0000 Received: (qmail 1930 invoked by uid 22791); 22 Feb 2006 19:23:19 -0000 X-Spam-Check-By: sourceware.org Received: from romy.inter.net.il (HELO romy.inter.net.il) (192.114.186.66) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 22 Feb 2006 19:23:18 +0000 Received: from HOME-C4E4A596F7 (IGLD-83-130-205-93.inter.net.il [83.130.205.93]) by romy.inter.net.il (MOS 3.7.3-GA) with ESMTP id DPR73558 (AUTH halo1); Wed, 22 Feb 2006 21:22:13 +0200 (IST) Date: Wed, 22 Feb 2006 19:25:00 -0000 Message-Id: From: Eli Zaretskii To: gdb@sourceware.org In-reply-to: <20060221213324.GA30729@nevyn.them.org> (message from Daniel Jacobowitz on Tue, 21 Feb 2006 16:33:24 -0500) Subject: Re: Quoting, backslashes, CLI and MI Reply-to: Eli Zaretskii References: <20060221213324.GA30729@nevyn.them.org> 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/msg00301.txt.bz2 > Date: Tue, 21 Feb 2006 16:33:24 -0500 > From: Daniel Jacobowitz > > I think that we want to continue using buildargv-style quoting for CLI > commands, and that it would be desirable to use only MI-style > quoting for MI commands. I agree. But that means MI commands that delegate to CLI will have to process the arguments to modify the quoting, right? > So I think that we should take this opportunity to fix up all MI > commands to quote like the documentation says they do. It would be good to fix that now, yes. However, I Think we need 2 different styles of quoting: one for file names, the other for strings. Otherwise, supporting the Windows backslashes will be hard. Also, there are messy cases such as this: (gdb) break "foo bar.c":'MyClass::MyMethod' (I'm not even sure I quoted it correctly ;-). Can we really use the same quoting rules for both the file-name and class/method name in such situations? > I'd like to fix up all the CLI and "set" commands to use buildargv style > quoting, too. If you agree with me on the two quoting styles, you will also agree that we need two different flavors of buildargv. > Andrew Cagney pointed out in a PR that we might need to update the > readline filename completion, too. I'm not sure if that's still relevant, > it needs a third look. It's relevant, at least wrt backslashes in Windows file names: if you type TAB with backslash being the last character, completion won't work (it does TRT when there are backslashes further to the left of the cursor, though). Also, quoted file names, with or without whitespace, aren't completed correctly, no matter if they use forward or backslashes.