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 |
I'm pretty sure the cywin shell actually is bash. Jerry Feldman wrote: > 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: >> Jerry Feldman wrote: >>> Gary Johnson wrote: >>>> ...it took me a day to figure out you needed a . in front of it to >>>> get it to execute. >>> >>> Usually, the current directory is not included because of well >>> documented hacks. So, when you type a command name, it will only >>> search the $PATH. To run something from any directory not in $PATH >>> you need the full path (beginning with /) or a relative path >>> beginning with ./. $HOME and ~ are essentially full paths. >> >> The OP might have been referring to: >> >> % ./script >> >> providing script was marked as executable, in which case your >> explanation applies, or he could have been referring to: >> >> % . script >> >> which is just a shortcut for: >> >> % source script >> >> -Tom >> > > > ------------------------------------------------------------------------ > > _______________________________________________ > Discuss mailing list > Discuss-mNDKBlG2WHs at public.gmane.org > http://lists.blu.org/mailman/listinfo/discuss > -- John Abreau IT Manager Zuken USA 238 Littleton Rd., Suite 100 Westford, MA 01886 T: 978-392-1777 F: 978-692-4725 M: 978-764-8934 E: John.Abreau-3flU0AWMlV4AvxtiuMwx3w at public.gmane.org W: www.zuken.com
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |