Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Date:	Fri, 12 Jan 2001 14:02:43 -0500
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	Cygwin <cygwin AT cygwin DOT com>
Subject:	Re: "The PATH problem"
Message-ID:	<20010112140243.C9768@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	Cygwin <cygwin AT cygwin DOT com>
References:	<3A5F15A2 DOT F8D56ABC AT yahoo DOT com> <200101121802 DOT KAA13233 AT prosper DOT leonora DOT org>
Mime-Version:	1.0
User-Agent:	Mutt/1.3.11i
In-Reply-To:	<200101121802.KAA13233@prosper.leonora.org>; from vladimir@acm.org on Fri, Jan 12, 2001 at 10:02:38AM -0800

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

>"EB" == Earnie Boyd <earnie_boyd AT yahoo DOT com> writes:
>
>  EB> Soren Andersen wrote:
>  >>
>  >> On 12 Jan 2001, an entity purporting to be Schaible, Joerg
>  >> [Schaible, Joerg <Joerg DOT Schaible AT gft DOT com>] wrote [regarding RE:
>  >> "The PATH problem"]
>  >>
>  >> > Hi Soren,
>  >> >
>  >> > >Cygwin doesn't allow modification or unset on the PATH variable
>  >> > >after login, so it has to be set right from 'Doze before bash
>  >> > >gets fired up, no?
>  >> >
>  >> > Who has told you that? This is simply not true, but it depends on
>  >> > the shell you're using.
>  >>
>  >> I am *quite* sure I just read it in documentation, but I am sorry,
>  >> I have been multitasking at least a half-dozen projects for days
>  >> now, and I do not have a pointer to cite to the location of this
>  >> statement.
>  >>
>  >> I exhaustively tried to alter my PATH inside bash (using statements
>  >> identical to what you cited) before I found the documentary
>  >> confirmation that it doesn't work.
>  >>
>  >> "YMMV".
>  >>
>
>  EB> YMMV??? Joerg is correct. This is an impartial nature of the
>  EB> shell, all shells, including command.com and cmd.exe. I don't
>  EB> think that your systems are a special case, but YMMV.
>
>  EB> Cheers, Earnie.

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -