At 02:02 PM 1/12/2001, you wrote:
>On Fri, Jan 12, 2001 at 10:02:38AM -0800, Vladimir G Ivanovic wrote:
> >Could you be confusing setting PATH with setting CYGWIN? A subsequent
> >message to this email list mentions that CYGWIN must be set before
> >cygwin1.dll is loaded.
>
>Probably. For a while I generalized the proviso against setting CYGWIN in
>a bash shell to mean that *no* commands would work at all unless I typed
>them prior to running bash. This seemed sort of silly and I almost
>complained bitterly to the cygwin mailing list.
>
>I spent many a long lonely night looking at the bash prompt and
>wondering how I could get any work done, finally rebooting my machine so
>that I could at least get back the Windows command window. It finally
>occurred to me that I should just try typing something to see if it
>worked.
>
>It did work, of course. bash accepted commands just fine. I guess that
>makes sense in retrospect...
>
>But now I'm really confused since the CYGWIN problem still seems to
>be there. I type CYGWIN at the command prompt and it says:
>
>bash: CYGWIN: command not found
>
>Go figure.
>
>cgf
Hm, this really frightens me. I think I'm going to put Cygwin away for a
while and go play with my other toys...
Larry Hall [EMAIL PROTECTED]
RFK Partners, Inc. http://www.rfk.com
118 Washington Street (508) 893-9779 - RFK Office
Holliston, MA 01746 (508) 893-9889 - FAX
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
