RE: source command broken in bash

2002-11-26 Thread Bryan Higgins
Found it--there was a file "x" in /usr/bin. The "which" command didn't find it, for some reason. Thanks for checking. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ:

RE: source command broken in bash

2002-11-26 Thread Larry Hall (RFK Partners, Inc)
At 05:34 PM 11/26/2002, Bryan Higgins wrote: >It turns out I was trying to source a file named x, and x appears to be spe- >cial in Cygwin. If I type x (after deleting my file x), I get the gawk usage. >There are no aliases to x, and "whence x" yields nothing. If I then exit the >shell will ^D, I

RE: source command broken in bash

2002-11-26 Thread Bryan Higgins
It turns out I was trying to source a file named x, and x appears to be spe- cial in Cygwin. If I type x (after deleting my file x), I get the gawk usage. There are no aliases to x, and "whence x" yields nothing. If I then exit the shell will ^D, I get a bunch of other crap. If you could confirm

RE: source command broken in bash

2002-11-26 Thread [EMAIL PROTECTED]
Type the following in your bash prompt: unalias source unalias . You'll need to find which of your local script files alias these commands to gawk and remove these settings if the aliases are not to your liking. I suppose there's some possibility that you have created some links (symbolic or