From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MRDKR-0005Pn-VC for qemu-devel@nongnu.org; Wed, 15 Jul 2009 18:52:00 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MRDKM-0005Ln-Ph for qemu-devel@nongnu.org; Wed, 15 Jul 2009 18:51:58 -0400 Received: from [199.232.76.173] (port=46041 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MRDKM-0005La-Dy for qemu-devel@nongnu.org; Wed, 15 Jul 2009 18:51:54 -0400 Received: from mail2.shareable.org ([80.68.89.115]:49155) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MRDKL-0000lX-Px for qemu-devel@nongnu.org; Wed, 15 Jul 2009 18:51:54 -0400 Date: Wed, 15 Jul 2009 23:51:51 +0100 From: Jamie Lokier Subject: Re: [Qemu-devel] [PATCH] rev3: support colon in filenames Message-ID: <20090715225150.GU3056@shareable.org> References: <4A4C754D.10109@redhat.com> <4A4CAD86.9020607@us.ibm.com> <4A4CB39F.5070506@redhat.com> <20090715181405.GB3056@shareable.org> <4A5E4206.20602@web.de> <20090715213635.GN3056@shareable.org> <4A5E4D33.9070901@web.de> <4A5E5545.5060603@us.ibm.com> <20090715223949.GS3056@shareable.org> <4A5E5B00.10304@us.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A5E5B00.10304@us.ibm.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Kevin Wolf , linuxram@us.ibm.com, Jan Kiszka , qemu-devel@nongnu.org, kvm-devel Anthony Liguori wrote: > Jamie Lokier wrote: > >Anthony Liguori wrote: > > > >>Jan Kiszka wrote: > >> > >>>We would still have to deal with the fact that so far '\' had no special > >>>meaning on Windows - except that is was the well-known path separator. > >>>So redefining its meaning would break a bit... > >>> > >>> > >>That's the problem. You will break existing Windows users. > >> > >>I know this goes against the current momentum in qemu, but overloading > >>one option with a bunch of parameters seems absolutely silly to me. > >> > >>IMHO, -drive file=foo.img,if=virtio,cache=off should have always been at > >>least three parameters. > >> > > > >That's fine for command lines. I don't necessarily disagree with you. > > > >But how do you propose to handle paths in monitor commands, when the > >path contains a space/quote/whatever as it often does on Windows ("My > >Documents", "Program Files")? > > > > Same basic rules apply. The monitor should use shell-style quoting. So instead of consistency, you like the idea of using different quoting rules for the monitor than for command line arguments? -- Jamie