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
From:	"Matthew Swift" <swift AT alum DOT mit DOT edu>
To:	<cygwin AT cygwin DOT com>
Subject:	dox ought to recommend setting CYGWIN in Windows environment
Date:	Wed, 25 Sep 2002 02:48:19 -0400
Message-ID:	<000001c2645f$8ca4b370$55983118@swift.xxx>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
Importance:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1106

When using Cygwin programs with a graphical ui like GTK, it is natural
to think of launching them directly from a Windows shortcut.  For
example, one can launch the unison file synchronizer this way.  These
processes will not have CYGWIN set appropriately in their environment,
unless CYGWIN is set as a Windows environment variable.  For example,
the presence of the "ntsec" flag is crucial to unison.

I believe the Cygwin documentation for setting up Cygwin (that is,
http://cygwin.com/cygwin-ug-net/setup-env.html) ought to recommend that
CYGWIN be set in the Windows environment (along with modification of
PATH) for this reason.

Another advantage of doing so is that one can then launch an interactive
bash shell without the cygwin.bat file and its additional overhead.
Simply create a shortcut directly to bash.exe with the arguments
"--login -i".

 



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -