From: Andrey Repin <anrdaemon@freemail.ru>
To: Aaron Schneider <notstop@users.sourceforge.net>, cygwin@cygwin.com
Subject: Re: Inconsistence on file operation when the name already exists with exe extension
Date: Wed, 11 Jul 2012 00:50:00 -0000 [thread overview]
Message-ID: <398013297.20120711044156@mtu-net.ru> (raw)
In-Reply-To: <BLU0-SMTP212B1E87711B5FCCCC6A04DCED20@phx.gbl>
Greetings, Aaron Schneider!
>>> Probably compiling binaries under cygwin without the exe extension, like
>>> unix, is not an alternative, or is it? Cygwin may detect if it is
>>> executable checking if it's PE format; if it is perl script. Just check
>>> if file is present in path or run. /file
>>
>> False. It is wholly possible, you just have to pass the correct flags
>> to the linker process. Current windows versions since at least XP and
>> maybe before would run files that did not contain a .exe extension.
>>
> I don't see how you can run a PE executable from windows shell (cmd.exe)
You're comparing apples to oranges.
You've been told already that Cygwin doesn't try to emulate windows shells or
anything of that kind.
> directly without the exe extension. I've just tried it in several ways
> and always prompts me the "Open with..." dialog instead of directly
> running it because treats it as data.
> When you say that Windows XP and above can run an executable without
> extension, you are talking about running it from windows shell.
No, he's talking about CreateProcess[Ex]() function call.
It's possible to execute binary with arbitrary name, since at least Win NT 4.x
if memory serves me well.
> But I was referring in the end to the cygwin terminal
> (C:\cygwin\bin\mintty.exe -) that I believe can run exe without
> extension even in older versions of windows, because it's bash that
> launches it as you said before.
You're confusing shell with terminal... don't you?
Try
mintty.exe -h -e C:\WINDOWS\system32\cmd.exe /K
You'll be surprised.
> That's being said because I expect users to run commands from the cygwin
> terminal. The exe extension is needed if you want to run the linux
> commands directly from the windows shell directly (c:\cygwin\bin\ and
> other bash PATHs should be exported to the windows PATH to run them
> directly from windows shell, but you will mix things up)
I do like to mix things. Alot. Life is just not the same without that.
--
WBR,
Andrey Repin (anrdaemon@freemail.ru) 11.07.2012, <04:32>
Sorry for my terrible english...
--
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:[~2012-07-11 0:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 15:23 notstop
2012-07-09 15:45 ` Christopher Faylor
2012-07-09 16:47 ` Steven Hartland
2012-07-09 17:20 ` Aaron Schneider
2012-07-10 5:38 ` Matt Seitz
2012-07-10 8:45 ` Aaron Schneider
2012-07-10 15:25 ` Earnie Boyd
2012-07-10 16:23 ` Larry Hall (Cygwin)
2012-07-10 16:54 ` Aaron Schneider
2012-07-10 17:03 ` Christopher Faylor
2012-07-10 18:59 ` Earnie Boyd
2012-07-11 0:50 ` Andrey Repin [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-07-08 20:03 Aaron Schneider
2012-07-08 20:19 ` Aaron Schneider
2012-07-08 20:27 ` marco atzeri
2012-07-08 20:37 ` Aaron Schneider
2012-07-09 12:36 ` Earnie Boyd
2012-07-08 20:49 ` Aaron Schneider
2012-07-08 22:43 ` Buchbinder, Barry (NIH/NIAID) [E]
2012-07-08 23:20 ` Andrey Repin
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=398013297.20120711044156@mtu-net.ru \
--to=anrdaemon@freemail.ru \
--cc=cygwin@cygwin.com \
--cc=notstop@users.sourceforge.net \
/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).