From: Herbert Stocker <hersto@gmx.de>
To: cygwin@cygwin.com
Subject: Re: cygpath -w and .exe magic
Date: Fri, 26 Aug 2016 14:30:00 -0000 [thread overview]
Message-ID: <57C04920.1040500@gmx.de> (raw)
In-Reply-To: <c9135e59-684e-f749-9fd7-c14b64bae105@mitel.com>
On 26.08.2016 15:19, Lee Dilkie wrote:
>
>
> On 8/26/2016 9:08 AM, Nellis, Kenneth wrote:
>> Dear Cygwin Community,
>>
>> $ ls -l
>> total 60
>> -rwxr-x--- 1 knellis Domain Users 60927 Aug 26 08:57 hello.exe
>> $ ./hello
>> Hello, world!
>> $ cygpath -w hello
>> hello
>> $
>>
>> The purpose of cygpath -w, it seems to me, is to provide
>> to Windows a valid path given a Posix path.
>>
>> Given executable file foo.exe, which Cygwin allows to be
>> referenced simply as foo, should not: cygpath -w foo
>> return: foo.exe
>> instead of: foo
>> ?
>>
>> Passing foo to a Windows application will certainly
>> be a problem. I recognize this might be considered a
>> change of scope for the program, but I think the tool
>> should do the .exe magic rather than pass off this
>> responsibility to the user. Food for thought.
>
> and break everyone who has existing code to take care of this?
If it is done, it should be done as an additional option, i'd say.
Herbert
>
> --
> 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
>
--
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:[~2016-08-26 13:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 13:59 Nellis, Kenneth
2016-08-26 14:30 ` Lee Dilkie
2016-08-26 14:30 ` Herbert Stocker [this message]
2016-08-26 14:58 ` Nellis, Kenneth
2016-08-26 15:07 ` cyg Simple
2016-08-26 15:34 ` Nellis, Kenneth
2016-08-26 17:55 ` Erik Soderquist
2016-08-26 19:50 ` cyg Simple
2016-08-26 14:45 ` cyg Simple
2016-08-26 15:29 ` Doug Henderson
2016-08-26 16:50 ` Herbert Stocker
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=57C04920.1040500@gmx.de \
--to=hersto@gmx.de \
--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).