From: Dmitry Bely <dbely@mail.ru>
To: cygwin@cygwin.com
Subject: Multiple backslashes
Date: Sun, 10 Feb 2002 08:55:00 -0000 [thread overview]
Message-ID: <sn891e0t.fsf@mail.ru> (raw)
This is probably a FAQ, but can you explain me why
bash -c "ls c:\\\\"
requires 4 backslashes? I can understand why 2 BS is needed, but 4 BS IMHO
are too much :-)
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 reply other threads:[~2002-02-10 16:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-10 8:55 Dmitry Bely [this message]
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 ` 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=sn891e0t.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).