public inbox for cygwin-patches@cygwin.com
 help / color / mirror / Atom feed
* patch for command line containing equals sign
@ 2014-03-20 21:10 Weber, Mark
  2014-03-20 22:15 ` Christopher Faylor
  0 siblings, 1 reply; 2+ messages in thread
From: Weber, Mark @ 2014-03-20 21:10 UTC (permalink / raw)
  To: cygwin-patches


See
http://cygwin.com/ml/cygwin-patches/2014-q1/msg00017.html
and related.

Thanks for posting how the new behavior is different from the old.
I am having a related issue, with C++ code that parses the command line.

The command line we support is something like -
  program_name   arg1  -option1=val1  -option2=val2  ...

You get the idea.

Now, with the above mentioned Cygwin patch, we are seeing the input arguments

arg1  "-option1=val1"   "-option2=val2"  ...

If this were the extent of the issue, it would be no big deal to strip off the quotes. However, the user may have put quotes on the command line himself, which Cygwin now moves around.
Such as:
  program_name  arg1  -option1="file name with spaces in it"

Is there any way to reliably tell what the user entered on the command line?



^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: patch for command line containing equals sign
  2014-03-20 21:10 patch for command line containing equals sign Weber, Mark
@ 2014-03-20 22:15 ` Christopher Faylor
  0 siblings, 0 replies; 2+ messages in thread
From: Christopher Faylor @ 2014-03-20 22:15 UTC (permalink / raw)
  To: cygwin-patches

On Thu, Mar 20, 2014 at 09:10:05PM +0000, Weber, Mark wrote:
>
>See
>http://cygwin.com/ml/cygwin-patches/2014-q1/msg00017.html
>and related.
>
>Thanks for posting how the new behavior is different from the old.
>I am having a related issue, with C++ code that parses the command line.
>
>The command line we support is something like -
>  program_name   arg1  -option1=val1  -option2=val2  ...
>
>You get the idea.
>
>Now, with the above mentioned Cygwin patch, we are seeing the input arguments
>
>arg1  "-option1=val1"   "-option2=val2"  ...
>
>If this were the extent of the issue, it would be no big deal to strip off the quotes. However, the user may have put quotes on the command line himself, which Cygwin now moves around.
>Such as:
>  program_name  arg1  -option1="file name with spaces in it"
>
>Is there any way to reliably tell what the user entered on the command line?

Sorry but this mailing list is for patches, not questions or bug reports.

I'm unsubscribing you from this list.  Please resubscribe if you have an actual
patch to submit.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2014-03-20 22:15 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-03-20 21:10 patch for command line containing equals sign Weber, Mark
2014-03-20 22:15 ` Christopher Faylor

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).