From: Laurent Vivier <Laurent.Vivier@bull.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH] Fix double backslash problem in Windows
Date: Thu, 10 Jan 2008 20:21:15 +0100 [thread overview]
Message-ID: <1199992875.4713.2.camel@frecb07144> (raw)
In-Reply-To: <fm5pu0$f36$1@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1378 bytes --]
Le jeudi 10 janvier 2008 à 10:59 -0800, consul a écrit :
> "Avi Kivity" <avi@qumranet.com> wrote in message
> news:47861E01.6050709@qumranet.com...
> > Johannes Schindelin wrote:
> >> Hi,
> >>
> >> On Thu, 10 Jan 2008, Laurent Vivier wrote:
> >>
> >>
> >>> Perhaps the best solution is to put "file=" option at the end of
> >>> aliases, '\0' is marking the end of filename (it is likely the idea of
> >>> andrzej about special characters).
> >>>
> >>
> >> Oh, why not just make it a requirement that file= comes last, always?
> >>
> >>
> >
> > That's hardly intuitive. I would prefer some sort of escaping for \, and
> > \=. It will also break if/when -drive gains another filename argument
> > (say, for keeping shapshot data in).
> >
> > --
> > error compiling committee.c: too many arguments to function
> >
> >
> >
> >
>
> Why not use double quotes around parameter values containing special
> characters?
It is currently what it is implemented. If you use double quote, you
must an escape character to be able to have double-quote inside, for
instance: file="my\"file". And backslash has some problems with
windows...
Laurent
--
----------------- Laurent.Vivier@bull.net ------------------
"La perfection est atteinte non quand il ne reste rien à
ajouter mais quand il ne reste rien à enlever." Saint Exupéry
[-- Attachment #2: Ceci est une partie de message numériquement signée --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-01-10 19:20 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 16:17 [Qemu-devel] [PATCH] Fix double backslash problem in Windows Hervé Poussineau
2008-01-09 9:31 ` Laurent Vivier
2008-01-09 9:51 ` andrzej zaborowski
2008-01-09 10:04 ` Laurent Vivier
2008-01-09 10:40 ` andrzej zaborowski
2008-01-09 12:08 ` Laurent Vivier
2008-01-09 12:27 ` Johannes Schindelin
2008-01-09 12:51 ` Laurent Vivier
2008-01-09 13:27 ` Johannes Schindelin
2008-01-09 13:46 ` Laurent Vivier
2008-01-09 13:56 ` andrzej zaborowski
2008-01-09 14:45 ` Laurent Vivier
2008-01-09 13:59 ` Johannes Schindelin
2008-01-09 14:42 ` Laurent Vivier
2008-01-10 9:35 ` Laurent Vivier
2008-01-10 11:53 ` Johannes Schindelin
2008-01-10 12:12 ` Laurent Vivier
2008-01-10 12:15 ` Johannes Schindelin
2008-01-10 12:33 ` Laurent Vivier
2008-01-10 13:30 ` Avi Kivity
2008-01-10 13:58 ` Laurent Vivier
2008-01-10 14:18 ` [Qemu-devel] " Jernej Simončič
2008-01-10 15:02 ` Laurent Vivier
2008-01-10 18:13 ` Laurent Vivier
2008-01-11 9:01 ` Laurent Vivier
2008-01-10 18:59 ` [Qemu-devel] Re: [PATCH] " consul
2008-01-10 19:21 ` Laurent Vivier [this message]
2008-01-09 12:27 ` [Qemu-devel] " Andreas Färber
2008-01-09 13:24 ` Laurent Vivier
2008-01-09 12:44 ` andrzej zaborowski
2008-01-09 17:53 ` Anthony Liguori
2008-01-09 18:23 ` Johannes Schindelin
2008-01-09 19:11 ` Laurent Vivier
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=1199992875.4713.2.camel@frecb07144 \
--to=laurent.vivier@bull.net \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).