Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
If I recall it was ksh. On 11/13/2008 10:31 AM, John Abreau wrote: > I'm pretty sure the cywin shell actually is bash. > > > Jerry Feldman wrote: > =20 >> That's a good point, but I don't think that the '. script' applies to = >> CYGWIN as AFAIK, CYGWIN does not use BASH. >> >> On 11/12/2008 04:45 PM, Tom Metro wrote: >> =20 >>> Jerry Feldman wrote: >>> =20 >>>> Gary Johnson wrote: >>>> =20 >>>>> ...it took me a day to figure out you needed a . in front of it to >>>>> get it to execute. >>>>> =20 >>>> Usually, the current directory is not included because of well=20 >>>> documented hacks. So, when you type a command name, it will only=20 >>>> search the $PATH. To run something from any directory not in $PATH=20 >>>> you need the full path (beginning with /) or a relative path=20 >>>> beginning with ./. $HOME and ~ are essentially full paths. >>>> =20 >>> The OP might have been referring to: >>> >>> % ./script >>> >>> providing script was marked as executable, in which case your=20 >>> explanation applies, or he could have been referring to: >>> >>> % . script >>> >>> which is just a shortcut for: >>> >>> % source script >>> >>> -Tom >>> >>> =20 >> ----------------------------------------------------------------------= -- >> >> _______________________________________________ >> Discuss mailing list >> Discuss-mNDKBlG2WHs at public.gmane.org >> http://lists.blu.org/mailman/listinfo/discuss >> =20 >> =20 > > =20 --=20 Jerry Feldman <gaf-mNDKBlG2WHs at public.gmane.org> Boston Linux and Unix PGP key id: 537C5846 PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB CA3B 4607 4319 537C 5846
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |