This is the mail archive of the 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: faq: why doesn't tilde expansion work in shell scripts in cyg win?

Oops, you're right.  Cygwin setup puts an icon to bash on the desktop,
so the ~ expansion I saw was by bash.

I have nothing against a speedy /bin/sh, but it seems rather short-sighted
to use a non-posix-compliant one.  Has anyone put ash (as compiled for
Cygwin) through any posix compliance tests?  Maybe all we need to do
is enable ~ expansion to become compliant... it's there in ash, just 
ifdef'd out.

- Dan

-----Original Message-----
From: Randall R Schulz

At 21:02 2002-08-24, Dan Kegel wrote:
>Aha. I figured it out, and it looks like Cygwin's ash might not be
>compliant. Tilde expansion is required by Posix; see 
>Looking at the source for the ash used in Cygwin, it looks like tilde 
>expansion is disabled! The in 
>defines SMALL by default, which shuts off tilde expansion. That would 
>explain my result (though not why tilde works from the ash commandline;


Please explain "works from the ash commandline." I can see no
in which tilde expansion is happening in ash.

>Am I correct?  It's a little suprising to find Cygwin doesn't use a 
>Posix-compliant shell...

As I understand it, Cygwin includes ash specifically as a
shell for scripting and makefiles. It's small size and minimal feature
gives it a low start-up time, which helps a lot when many of them get 
executed, for example when running make.

>- Dan

Randall Schulz
Mountain View, CA USA

Unsubscribe info:
Bug reporting:

Unsubscribe info:
Bug reporting:

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