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
On Tue, Jul 10, 2012 at 12:54 PM, Aaron Schneider wrote:
> I don't see how you can run a PE executable from windows shell (cmd.exe)
> 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 tre
On Tue, Jul 10, 2012 at 06:54:06PM +0200, Aaron Schneider wrote:
>On 10/07/2012 17:24, Earnie Boyd wrote:
>> On Tue, Jul 10, 2012 at 4:34 AM, Aaron Schneider
>>> You're right that cygwin shell tries to emulate bash, I just twisted things.
>>>
>>
>> You're still wrong. Cygwin is a POSIX library for
On 10/07/2012 17:24, Earnie Boyd wrote:
On Tue, Jul 10, 2012 at 4:34 AM, Aaron Schneider
You're right that cygwin shell tries to emulate bash, I just twisted things.
You're still wrong. Cygwin is a POSIX library for Windows. Bash is a
shell capable of being built with that POSIX library for
On 7/10/2012 11:24 AM, Earnie Boyd wrote:
On Tue, Jul 10, 2012 at 4:34 AM, Aaron Schneider wrote:
You're right that cygwin shell tries to emulate bash, I just twisted things.
You're still wrong. Cygwin is a POSIX library for Windows. Bash is a
shell capable of being built with that POSIX li
On Tue, Jul 10, 2012 at 4:34 AM, Aaron Schneider
wrote:
> You're right that cygwin shell tries to emulate bash, I just twisted things.
>
You're still wrong. Cygwin is a POSIX library for Windows. Bash is a
shell capable of being built with that POSIX library for use on
Windows but it isn't an e
Matt Seitz escribió:
>> On Behalf Of Aaron Schneider
>>
>> I believe that Cygwin tries to emulate cmd.exe
>
>No, Cygwin does not try to emulate the cmd.exe shell. Cygwin tries to
>emulate a shell running on Linux, usually the "bash" shell.
>
>That's why you have to use "./file.exe" or "./file" t
On 09/07/2012 17:44, Christopher Faylor wrote:
On Mon, Jul 09, 2012 at 05:23:13PM +0200, notstop wrote:
You must be right in some points, but that is not the exact behavior of
windows command although you pretend it to be (the powershell has a
different behavior). In fact, I can independently op
- Original Message -
From: "Christopher Faylor"
On Mon, Jul 09, 2012 at 05:23:13PM +0200, notstop wrote:
You must be right in some points, but that is not the exact behavior of
windows command although you pretend it to be (the powershell has a
different behavior). In fact, I can inde
On Mon, Jul 09, 2012 at 05:23:13PM +0200, notstop wrote:
>You must be right in some points, but that is not the exact behavior of
>windows command although you pretend it to be (the powershell has a
>different behavior). In fact, I can independently operate file while
>file.exe exists:
>
>copy f
You must be right in some points, but that is not the exact behavior of
windows command although you pretend it to be (the powershell has a
different behavior). In fact, I can independently operate file while
file.exe exists:
copy file.exe file
Now there are file and file.exe
-- windows cmd.e
On Sun, Jul 8, 2012 at 4:37 PM, Aaron Schneider wrote:
>
>
>
> -- This way works to have the two files simultaneously --:
> touch file
> touch file.exe
>
> -- This way doesn't --:
> touch file.exe
> touch file
Add a period character to the file name without extension. Cygwin
will consider file.ex
Greetings, Aaron Schneider!
> --On an empty dir--:
> touch file.exe
> touch file.img
> touch file doesn't create the corresponding file.
> --Then--
> touch helpp
> cp helpp file
> cp: can't create regular file «file»: File exists
> On rm file it removes the file.exe instead of saying file
Aaron Schneider wrote: on July 08, 2012 at 4:19 PM
> Is this behavior intended? This is not unix like, the filename should be
> preserved as is.
This may help explain this behavior:
http://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-exe
--
Problem reports: http://cygwin.com
Since for creating file and file.exe in cygwin, the file without exe must be
created first to have both, under windows you can follow any order:
Using Windows 7 PowerShell:
-- This works --
fsutil file createnew file.exe 0
fsutil file createnew file 0
-- This works as well --
fsutil file cr
-- This way works to have the two files simultaneously --:
touch file
touch file.exe
-- This way doesn't --:
touch file.exe
touch file
-- This works again and is similar to 1st --:
touch file.exe && bzip2 file.exe
touch file
bzip2 -d file.exe.bz2
How can this be?
On 7/8/2012 10:19 PM, Aaron Schneider wrote:
--On an empty dir--:
touch file.exe
touch file.img
touch file doesn't create the corresponding file.
--Then--
touch helpp
cp helpp file
cp: can't create regular file «file»: File exists
On rm file it removes the file.exe instead of saying file
--On an empty dir--:
touch file.exe
touch file.img
touch file doesn't create the corresponding file.
--Then--
touch helpp
cp helpp file
cp: can't create regular file «file»: File exists
On rm file it removes the file.exe instead of saying file not found.
Is this behavior intended? This is
18 matches
Mail list logo
