Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com User-Agent: Mutt/1.4i Hamster-Fr/2.0.1.10 Date: Thu, 12 Dec 2002 23:50:44 +0100 From: Luc Hermitte To: cygwin AT cygwin DOT com Subject: [ANN] Re: cyg-wrapper.sh Message-ID: <20021212225044.GA42218223@ORLYN> References: <20021206013757 DOT GA976927 AT ORLYN> <87adjd3k45 DOT fsf AT squeaker DOT lickey DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87adjd3k45.fsf@squeaker.lickey.com> Hello Matt, * On Tue, Dec 10, 2002 at 09:38:02AM -0700, Matt Armstrong wrote: > Luc, you might consider adding an option to unset the PWD environment > variable (or convert it to a Windows path). That's done. I haven't done any test with perforce, so, let me know. The two new options are: --cyg-PWD-clear : to unset PWD --cyg-PWD-convert : to convert PWD to its DOS (short) form. I was considering to handle other environment variables, but I didn't see any good candidate -- ie. environment variables specific to bash or cygwin that win32 native applications may also use. -- Luc Hermitte -- 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/