From: "Пётр Б." <satnatantas@gmail.com>
To: cygwin <cygwin@cygwin.com>
Subject: Re: Passing double quotes to DOS
Date: Sun, 03 May 2015 20:10:00 -0000 [thread overview]
Message-ID: <CA+Ni7jMCym9_txVuvoFCeV_3t8NV7CD68unR8WjKP9f6szx4hw@mail.gmail.com> (raw)
In-Reply-To: <CA+Ni7jMAtGL=xV2GoM5CCo282OdU1aDed++1kGX_UrrT=FbzFA@mail.gmail.com>
cygwin.com/ml/cygwin/2002-02/msg00336.html
There was a statement saying that cygwin does everything to preserve
double quotes.
It does not. I was recently doing some symbolic links with "cmd /c
mklink "path" "filename" " recently and it was fine until I had a file
with ampersand.
If I type
cmd /c mklink "path" "filename"
cmd.exe is called without doubleqoutes (I use ProcExp to see cmd line).
If I type same thing in "Run" dialog of TaskManager, doublequotes are
passed as intended.
If I type
cmd /c mklink \"path\" \"filename\"
reverse slash spills to cmd line.
If I type
cmd /c mklink "\"path\"" "\"filename\""
reverse slash and all doubleqoutes spill to cmd line.
I really do not get it. How do I pass doubleqoutes to CMD? Problem is
not related to mklink or any internals of CMD and even bash - Cygwin
does not pass doubleqoutes instead.
Example:
echo "\"bbb\""
cmd /c echo "\"bbb\""
There must be an error somewhere on the CYGWIN/Windows boundary.
Can I somehow whitelist "cmd.exe" so it does not get special treatment?
CYGWIN_NT-6.1 USER 1.7.33-2(0.280/5/3) 2014-11-13 15:47 x86_64 Cygwin
--
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
next prev parent reply other threads:[~2015-05-03 20:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+Ni7jNBd0WZu37OMiPEyvxwkgvYnDfonKoLjpuvNrZ95A9Rbw@mail.gmail.com>
2015-05-03 20:06 ` Пётр Б.
2015-05-03 20:10 ` Пётр Б. [this message]
2015-05-03 20:11 ` Пётр Б.
2015-05-03 20:21 ` Пётр Б.
2015-05-05 14:47 ` cyg Simple
2002-02-07 2:48 Richard Gilbert
2002-02-07 3:17 ` Pavel Tsekov
2002-02-07 3:30 ` Richard Gilbert
2002-02-07 8:21 ` Pavel Tsekov
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=CA+Ni7jMCym9_txVuvoFCeV_3t8NV7CD68unR8WjKP9f6szx4hw@mail.gmail.com \
--to=satnatantas@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).