From: Dmitry Bely <dbely@mail.ru>
To: Randall R Schulz <rrschulz@cris.com>
Cc: Dmitry Bely <dbely@mail.ru>, cygwin@cygwin.com
Subject: Re: Multiple backslashes
Date: Sun, 10 Feb 2002 10:35:00 -0000 [thread overview]
Message-ID: <heoprxub.fsf@mail.ru> (raw)
In-Reply-To: <5.1.0.14.2.20020210095957.023d7eb0@pop3.cris.com>
Randall R Schulz <rrschulz@cris.com> writes:
> What I said is accurate. However, in the absence of any explicit
> mention on your part, I assumed you were issuing the commands you
> specified from a Cygwin shell. It now appears you are entering them
> into CMD.exe.
>
> If I'm not mistaken, arguments are processed differently in Cygwin
> binaries when they are invoked from a Windows program than they are
> when invoked by another Cygwin process. Someone who knows better (or
> the manual...) will have to supply details, it's a mode of operation I
> never encounter (CMD.exe offends me deeply...). I have a vague
> recollection that there is a CYGWIN environment variable option that
> controls or supresses or modifies this behavior somehow--I'm even less
> sure about this than I am about the variant argument processing itself.
OK, I will look into it.
> I believe this is why you're experiencing difficulties. You'll have to
> familiarize yourself with the special argument processing in the
> Windows ->
>
> Cygwin transition.
>
> Or, you can do what I strongly suggest to everyone who'll listen:
> DON'T USE CMD.EXE!
Thank you very much for you comments, but I must repeat that in my case
XEmacs calls bash -c "..." _directly_ via CreateProcess() with _exactly_
the same results. So I still tend to consider the necessity of "\\\\" as a
bug.
Hope to hear from you soon,
Dmitry
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2002-02-10 18:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-10 8:55 Dmitry Bely
2002-02-10 9:13 ` Randall R Schulz
2002-02-10 9:55 ` Dmitry Bely
2002-02-10 10:12 ` Randall R Schulz
2002-02-10 10:35 ` Dmitry Bely [this message]
2002-02-10 10:58 ` Randall R Schulz
2002-02-10 11:55 ` Dmitry Bely
2002-02-10 14:50 ` Randall R Schulz
2002-02-11 1:35 ` a problem with search path? (was: Multiple backslashes) Dmitry Bely
2002-02-11 8:57 ` Randall R Schulz
2002-02-12 8:06 ` Dmitry Bely
2002-02-11 5:41 Multiple backslashes Robinow, David
2002-02-12 2:15 ` Dmitry Bely
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=heoprxub.fsf@mail.ru \
--to=dbely@mail.ru \
--cc=cygwin@cygwin.com \
--cc=rrschulz@cris.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).