From: Mike Wray <mike.wray@hpl.hp.com>
To: Steven Hand <Steven.Hand@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: xm create option parsing..
Date: Fri, 30 Jul 2004 09:19:00 +0100 [thread overview]
Message-ID: <410A0474.3090303@hpl.hp.com> (raw)
In-Reply-To: <E1BprRD-0008Hh-00@mta1.cl.cam.ac.uk>
Steven Hand wrote:
> As far as I can see, "xm create -c vmid=1" will create a domain and
> attach to its console while "xm create vmid=1 -c" won't.
>
> Any reason for this? The option parsing routines xm/opts.py and
> xm/create.py seems substantial enough.
>
It's an artifact of getopt - it stops parsing options at
the first non-option. So
xm create -c vmid=1
sets the -c option, whereas
xm create vmid=1 -c
doesn't.
It think there's a getopt flag to process options anywhere
in the args, but this is a problem for a multicommand like xm
that has its own options as well as subcommand options.
Basically options (-x, --x) have to precede args.
Mike
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
next prev parent reply other threads:[~2004-07-30 8:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-28 16:37 xm create option parsing Steven Hand
2004-07-28 16:45 ` Tom Wilkie
2004-07-28 17:10 ` Ian Pratt
2004-07-28 17:16 ` Tom Wilkie
2004-07-30 8:19 ` Mike Wray [this message]
2004-07-30 8:42 ` Steven Hand
2004-07-30 8:49 ` Ian Pratt
2004-07-30 9:08 ` Mike Wray
2004-07-30 9:16 ` Mike Wray
2004-07-30 9:59 ` Ian Pratt
2004-07-30 13:41 ` Mike Wray
2004-07-30 9:53 ` Ian Pratt
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=410A0474.3090303@hpl.hp.com \
--to=mike.wray@hpl.hp.com \
--cc=Steven.Hand@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.