public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: cyg Simple <cygsimple@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Run command in new window
Date: Wed, 27 Dec 2017 01:11:00 -0000	[thread overview]
Message-ID: <e12dbeac-a27f-4f41-42c6-d5467433c553@gmail.com> (raw)
In-Reply-To: <5a42a5d2.6d249d0a.a7449.95a4@mx.google.com>

On 12/26/2017 2:41 PM, Steven Penny wrote:
> On Tue, 26 Dec 2017 11:54:14, Dave Caswell wrote:
>> $ cygstart -v bash -c \'echo 1\;read \'
>> ShellExecute(NULL, "(null)", "bash", "-c 'echo 1;read '", "(null)", 1)
>> By escaping the quotes and semicolon so they get passed along intact,
>> the executed bash also gets an intact command string.
> 
> this is interesting, but it doesnt explain (or im not understanding) why
> it will
> accept a quoted string and not an escaped one. in a normal setting, these
> commands are identical:
> 
>    $ bash -c 'echo; read'
>    + bash -c 'echo; read'
> 
>    $ bash -c echo\;\ read
>    + bash -c 'echo; read'
> 
> but with cygstart this command works:
> 
>    cygstart bash -c '"echo; read"'
> 
> and this does not:
> 
>    cygstart bash -c 'echo\;\ read'

As I said earlier the quotes are interpreted by the shell executing the
command.  So the shell execing the cygstart command is not passing the
quote to the secondary bash session because it has interpreted them.  If
you want to pass quotes to the process on the command line then you need
to quote them or use a backslash on the quote to prevent the shell doing
the exec to process them.

$ cygstart bash -c \'echo 1\; read\'

-- 
cyg Simple

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2017-12-26 22:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-25  3:50 Steven Penny
2017-12-25  4:06 ` Andrey Repin
2017-12-25  4:37   ` Steven Penny
2017-12-25  4:54     ` Dave Caswell
2017-12-25  5:11       ` Steven Penny
2017-12-26 17:43         ` Dave Caswell
2017-12-26 18:54           ` Steven Penny
2017-12-26 19:12             ` Steven Penny
2017-12-26 19:41               ` Dave Caswell
2017-12-26 23:44                 ` Steven Penny
2017-12-27  1:11                   ` cyg Simple [this message]
2017-12-27  1:16                     ` Steven Penny
2017-12-27  1:38                       ` Jürgen Wagner
2017-12-27 22:46                         ` Steven Penny
2017-12-27  9:39                     ` Steven Penny
2017-12-28 12:07                       ` cyg Simple
2017-12-28 20:11                         ` Steven Penny
2017-12-26 22:44               ` cyg Simple

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=e12dbeac-a27f-4f41-42c6-d5467433c553@gmail.com \
    --to=cygsimple@gmail.com \
    --cc=cygwin@cygwin.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).