public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Dmitry Bely <dbely@mail.ru>
To: cygwin@cygwin.com
Subject: a problem with search path? (was: Multiple backslashes)
Date: Mon, 11 Feb 2002 01:35:00 -0000	[thread overview]
Message-ID: <8za0s6tx.fsf_-_@mail.ru> (raw)
In-Reply-To: <5.1.0.14.2.20020210144103.02846b60@pop3.cris.com>

Randall R Schulz <rrschulz@cris.com> writes:

> I'm trying to help you, but you seem insistent on just declaring
> Cygwin buggy. It is not and it is possible for you to resolve the
> problem. I gave you all the information you need to do so.
> 
> One last time, I'll answer your points...

Randall, of course it's up to you whether to answer or not. Nonetheless,
thank you for your comments. For everyone else, I don't claim that cygwin
is buggy (although it might be the case). I just trying to understand
what's going on and how to solve my very problems. Randall's advice to add
CYGWIN=noglob _partially_ solves them (yes, really, it makes 2 BS
sufficient then 'bash -c "ls c:\\"' is called via syscall
CreateProcess()). But:

How to write the following command with _backslashes_ to make it work?
Suppose we launch it from bash:

bash-2.05$ bash -c "ls c:\\\\cygwin\\\\bin\\\\ls.exe"
c:\cygwin\bin\ls.exe
bash-2.05$ bash -c "c:\\\\cygwin\\\\bin\\\\ls.exe"
bash: c:\cygwin\bin\ls.exe: command not found
bash-2.05$

CYGWIN=noglob does _not_ help.

How many backslahes should I put there?
But please check that it _really_ works before answering.

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/

  reply	other threads:[~2002-02-11  9:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-10  8:55 Multiple backslashes 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
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               ` Dmitry Bely [this message]
2002-02-11  8:57                 ` a problem with search path? (was: Multiple backslashes) Randall R Schulz
2002-02-12  8:06                   ` Dmitry Bely
2002-02-11  2:13 Stephan Mueller
2002-02-11  2:45 ` Dmitry Bely
2002-02-11 10:22 Stephan Mueller
2002-02-12  8:15 ` Dmitry Bely
2002-02-12 11:06 Stephan Mueller

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=8za0s6tx.fsf_-_@mail.ru \
    --to=dbely@mail.ru \
    --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).