This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: ls and wildcards


On Jul 14 10:26, Thrall, Bryan wrote:
> Karl M wrote on Tuesday, July 14, 2009 10:17 AM:
> 
> > Hi All...
> > 
> > I just noticed while looking around after updating dash that "ls
> /bin/*sh"
> > does not find bash and dash, but it does on my Fedora core 6 machine
> at work.
> > I see the issue in both 1.5 and 1.7, attached is an example in cygwin
> 1.7.  
> > 
> > Thanks,
> > 
> > ...Karl
> 
> I can reproduce this (for bash, anyway; I don't have dash installed),
> plus:
> 
> $ ls /bin/*sh.exe
> /bin/ash.exe   /bin/ksh.exe    /bin/ppmflash.exe  /bin/sh.exe
> /bin/tclsh.exe
> /bin/bash.exe  /bin/pdksh.exe  /bin/rsh.exe       /bin/ssh.exe
> /bin/wish.exe

That's expected behaviour.  bash.exe simply doesn't match *sh, it
only matches *sh.exe.

In theory, what we could do is to drop the .exe suffix in future.
On Windows NT it's not required to run an executable so it would
be safe to drop the suffix as far as Cygwin is concerned.

However, cmd as well as Windows Explorer don't identify executables
using the executability flag.  Both refuse to start executables
missing the .exe suffix.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]