delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sources.redhat.com/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
Date: | Wed, 30 Jul 2003 18:37:37 -0500 |
From: | Joshua Daniel Franklin <joshuadfranklin AT yahoo DOT com> |
To: | cygwin AT cygwin DOT com |
Subject: | RE: "Using Cygwin Effectively with Windows" -- Draft of new User's Guide section |
Message-ID: | <20030730183737.A4167@ns1.iocc.com> |
Mime-Version: | 1.0 |
User-Agent: | Mutt/1.2.5.1i |
> I would suggest adding a section on the PATH environment and its use > when invoking bash from DOS. I'm not sure what this means... maybe that you need to add c:\cygwin\bin to your DOS PATH to use the binaries from DOS? Could you provide a sample of what you mean? -- 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |