public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Gordon Grimes <Gordon_Grimes@symantec.com>
To: Eric Blake <eblake@redhat.com>, "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: regtool 2.11.1 need a way to specify leading "-" in values
Date: Wed, 23 Jan 2019 00:05:00 -0000	[thread overview]
Message-ID: <BN6PR16MB155481CCA6BFE570A13C3DDCE8990@BN6PR16MB1554.namprd16.prod.outlook.com> (raw)
In-Reply-To: <668589bf-266f-c995-6e8c-61af56a8a28a@redhat.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1438 bytes --]

Perfect!  Thanks much, Eric.

-----Original Message-----
From: Eric Blake <eblake@redhat.com> 
Sent: Tuesday, January 22, 2019 6:21 PM
To: cygwin@cygwin.com; Gordon Grimes <Gordon_Grimes@symantec.com>
Subject: Re: regtool 2.11.1 need a way to specify leading "-" in values

On 1/22/19 5:12 PM, Gordon Grimes wrote:
> I believe there is no way to specify values with leading "-" in regtool.  I expect the same applies to keys.  An "end of switch processing" switch would be useful, forcing 'regtool' to interpret all remaining arguments literally.

Fortunately, you are mistaken.  regtool uses getopt_long(), and therefore, like all other programs that use this, automatically inherits the POSIX rule that '--' is the marker for "end of switch processing".

> 
> Example:
> % regtool -s set '\HKCU\Environment\MAVEN_OPTS' "-Xms512m -Xmx3072m  -Dcom.sun.management.jmxremote"
> regtool: unknown option -- X
> Try `regtool --help' for more information.

Try:

regtool -s set '\HKCU\Environment\MAVEN_OPS' -- "-Xms512m -Xmx3072m -Dcom.sun.management.jmxremote"

--
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3226
Virtualization:  qemu.org | libvirt.org

\0ТÒÐÐ¥\a&ö&ÆVÒ\a&W\x06÷'G3¢\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒ÷\a&ö&ÆV×2æ‡FÖÀФd\x15\x13¢\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöf\x17\x12ðФFö7VÖVçF\x17F–öã¢\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöFö72æ‡FÖÀÐ¥Vç7V'67&–&R\x06–æfó¢\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöÖÂò7Vç7V'67&–&R×6–×\x06ÆPРÐ

      reply	other threads:[~2019-01-23  0:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-22 23:12 Gordon Grimes
2019-01-22 23:21 ` Eric Blake
2019-01-23  0:05   ` Gordon Grimes [this message]

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=BN6PR16MB155481CCA6BFE570A13C3DDCE8990@BN6PR16MB1554.namprd16.prod.outlook.com \
    --to=gordon_grimes@symantec.com \
    --cc=cygwin@cygwin.com \
    --cc=eblake@redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).