From: "Charli Li" <KBarticle889459@aim.com>
To: <cygwin@cygwin.com>
Subject: RE: PATHs in Windows and Cygwin
Date: Tue, 13 Jun 2006 21:34:11 -0400
Message-ID: <LLEBLEDLPAKFHFKGNDBMEEIHCBAA.KBarticle889459@aim.com>
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <20060613224824.GB8497@trixie.casa.cgf.cx>
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Oh, wrong thing entirely.  Before, on my box, if you use the normal command
prompt and set the PATH again, it won't be there.  Dunno how this got
resolved, but it got resolved.  Apologies for the spam.

Charli

> -----Original Message-----
> From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com]On Behalf
> Of Christopher Faylor
> Sent: Tuesday, June 13, 2006 6:48 PM
> To: cygwin@cygwin.com
> Subject: Re: PATHs in Windows and Cygwin
>
>
> On Tue, Jun 13, 2006 at 06:24:43PM -0400, Charli Li wrote:
> >You have to set yourself up with a Windows batch script before
> you can even
> >start GNU programs.
>
> No.  You don't.
>
> You just need to have, e.g., c:\cygwin\bin in your PATH, as Dave said.
> I'm not sure why you thought you needed to elaborate on this but there
> is no need to add a batch script to the equation.  It's all about the
> PATH.
>
> This shouldn't be too surprising to anyone with a modicum of experience
> with either Linux OR Windows.
>
> cgf
>


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/