delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-SWARE-Spam-Status: | No, hits=-5.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,TW_YG |
X-Spam-Check-By: | sourceware.org |
X-IronPortListener: | Outbound_SMTP |
X-IronPort-Anti-Spam-Filtered: | true |
X-IronPort-Anti-Spam-Result: | At4AABXp2k6cKEcW/2dsb2JhbABEmgiQJ34HgXIBAQEEEihPAgEIDScCEB8TFwENAQEEGxqHbZsFmkWKPmMEiC2EL41njE8 |
From: | "Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder AT niaid DOT nih DOT gov> |
To: | "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com> |
Date: | Sat, 3 Dec 2011 22:33:00 -0500 |
Subject: | RE: Will win32 style paths ever work in mksh on cygwin? |
Message-ID: | <0105D5C1E0353146B1B222348B0411A20A43ADEDCD@NIHMLBX02.nih.gov> |
References: | <4ED74766 DOT 7010301 AT yahoo DOT com> <748260321 DOT 20111201203028 AT mtu-net DOT ru> <CAGHJv4ceBgyO7RsBGYO_HOfSUr4fRaZrFytOvMeFOgr+=pXY5w AT mail DOT gmail DOT com> |
In-Reply-To: | <CAGHJv4ceBgyO7RsBGYO_HOfSUr4fRaZrFytOvMeFOgr+=pXY5w@mail.gmail.com> |
MIME-Version: | 1.0 |
X-IsSubscribed: | yes |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
X-MIME-Autoconverted: | from quoted-printable to 8bit by delorie.com id pB43XUmB019553 |
Chris Sutcliffe sent the following at Thursday, December 01, 2011 2:17 PM >Fundamentally, Cygwin has been pushing the use of POSIX paths for quite >some time (in fact it warns you when it encounters a DOS / Windows >path). As has been pointed out, many Cygwin utilities support DOS / >Windows paths (likely for historical reasons I suspect), but mksh will >not. To expand on the above, as I understand it, the reason cygwin understands Windows PATHs is so one can use Cygwin utilities in a cmd.exe prompt or in batch files. See also <http://cygwin.com/cygwin-ug-net/using.html#pathnames-win32>. Please consider whether cygpath might be of use: <man cygpath> <http://cygwin.com/faq/faq-nochunks.html#faq.using.converting-paths> <http://cygwin.com/cygwin-ug-net/using-utils.html#cygpath> - Barry Disclaimer: Statements made herein are not made on behalf of NIAID. -- 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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |