duplicate *.exe commands

Larry Hall (Cygwin) reply-to-list-only-lh@cygwin.com
Thu Apr 9 04:02:00 GMT 2009


Atom Smasher wrote:
> i'm coming from a *nix background, but i'm finding that cygwin makes 
> things suck less on windows.
> 
> one of the things that really annoys me are the duplicate *.exe commands...
>     cat & cat.exe
>     awk & awk.exe
>     sed & sed.exe
> 
> what a mess, especially when i use auto-complete in my shell.
> 
> i'm curious, could it cause problems if i delete all "*.exe" files from 
> my command hash? or should i first check that it's really a duplicate? ie;
>   if i have "/path/to/foo" and "/path/to/foo.exe" then foo.exe goes away
>   if i have "/path/to/bar.exe", but not "/path/to/bar", then bar.exe stays
> 
> it seems like the same list of things that get pruned either way, but 
> for the sake of portability i'm wondering if there would be problems 
> just getting rid of everything *.exe.

There are no duplicate *.exe commands.  All Cygwin executables contain the
exe extension as Windows prefers.  Cygwin tries to make things easier by
mapping "cat" to "cat.exe", for example, which is why it may look to you
like there are both in the Cygwin environment.  But look at 'c:\cygwin\bin'
in the Explorer and you'll see all the commands have the .exe extension.
If you get rid of one, you get rid of the other since they are the same.
Now, to anticipate your next question, '/usr/bin/cat.exe' and '/bin/cat.exe'
are not duplicates either.  See the results of typing 'mount'.

-- 
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
216 Dalton Rd.                          (508) 893-9889 - FAX
Holliston, MA 01746

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/



More information about the Cygwin mailing list