From: Andy Koppe <andy.koppe@gmail.com>
To: cygwin@cygwin.com
Subject: Re: How to pass parameters to a windows application
Date: Wed, 04 Aug 2010 19:40:00 -0000 [thread overview]
Message-ID: <AANLkTi=pB1yQcsBmWDcuCysSoi=RVAPSS+pf+UDfu-QG@mail.gmail.com> (raw)
In-Reply-To: <20100804112630.GT8324@calimero.vinschen.de>
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?
Andy
--
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
next prev parent reply other threads:[~2010-08-04 19:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 0:43 Jason Pyeron
2010-08-02 6:49 ` Dave Hylands
2010-08-02 9:31 ` Andy Koppe
2010-08-02 11:55 ` Harald Joerg
2010-08-02 11:57 ` Jason Pyeron
2010-08-02 23:17 ` Dave Hylands
2010-08-03 11:43 ` Andy Koppe
2010-08-03 11:26 ` Andy Koppe
2010-08-04 11:26 ` Corinna Vinschen
2010-08-04 19:40 ` Andy Koppe [this message]
2010-08-05 8:21 ` Corinna Vinschen
2010-08-02 11:57 ` Jason Pyeron
2010-08-02 15:55 ` Andrey Repin
2010-08-03 7:27 ` Csaba Raduly
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='AANLkTi=pB1yQcsBmWDcuCysSoi=RVAPSS+pf+UDfu-QG@mail.gmail.com' \
--to=andy.koppe@gmail.com \
--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).