delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-Spam-Check-By: | sourceware.org |
Date: | Thu, 5 Aug 2010 10:21:06 +0200 |
From: | Corinna Vinschen <corinna-cygwin AT cygwin DOT com> |
To: | cygwin AT cygwin DOT com |
Subject: | Re: How to pass parameters to a windows application |
Message-ID: | <20100805082106.GB4610@calimero.vinschen.de> |
Reply-To: | cygwin AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
References: | <E2B92C7CBBA64B158FA61FDD9DDC20BC AT phoenix> <AANLkTinVYGVHP9W8w-j1gudobfqZX1aNza0n2XoxqiqC AT mail DOT gmail DOT com> <AANLkTinSh1+kMob1K4VX-MDLNzu-VLK+VdyLatjkyCZJ AT mail DOT gmail DOT com> <7B35B979DF6941628DE9A6D131AA3909 AT phoenix> <AANLkTim1x04h2Rhk-rH8sg3Gc0CN=VASG6xVFwjb3Kyh AT mail DOT gmail DOT com> <20100804112630 DOT GT8324 AT calimero DOT vinschen DOT de> <AANLkTi=pB1yQcsBmWDcuCysSoi=RVAPSS+pf+UDfu-QG AT mail DOT gmail DOT com> |
MIME-Version: | 1.0 |
In-Reply-To: | <AANLkTi=pB1yQcsBmWDcuCysSoi=RVAPSS+pf+UDfu-QG@mail.gmail.com> |
User-Agent: | Mutt/1.5.20 (2009-06-14) |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Unsubscribe: | <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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 |
On Aug 4 20:40, Andy Koppe wrote: > On 4 August 2010 12:26, Corinna Vinschen wrote: > > It's a shame that not even the official Win32 APIs are always clean > > in terms of the long path name definition. > > Yep, and MSDN doesn't even seem to mention it. > > >> Therefore I'm wondering whether it wouldn't be better to address this > >> once and for all in cygwin_conv_path itself by doing what cygpath > >> does: assuming the resulting path fits into MAX_PATH, drop "\\?\" from > >> all long paths and turn "UNC\" into "\\". > > > > This is already implemented in cygwin_conv_path for some time, but > > only for the CCP_POSIX_TO_WIN_A case. Â I never expected that this would > > also be necessary for the wide char case. Â Anyway, I applied a matching > > patch. Â As long as the resulting wide char path is not longer than > > MAX_PATH, it will be stripped of the long path prefix. > > Great. Seems to be working fine for me. > > This allows dropping the equivalent hack from cygpath, doesn't it? Right, but it doesn't hurt either. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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 |