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 Date: Mon, 25 Apr 2005 10:33:00 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Wrong PATH and other env after starting bash Message-ID: <20050425143300.GC6543@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <200504221512 DOT j3MFCJw31354 AT lastovo DOT hermes DOT si> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i On Mon, Apr 25, 2005 at 12:36:26PM +0200, David Balazic wrote: >"Dave Korn" wrote in message >news:SERRANOg3Lch8cwNIEN000000e4 AT SERRANO DOT CAM DOT ARTIMI DOT COM... > >>If that still doesn't work, you're going to need to get your cygcheck >>output and post it **as an attachment** to the list; see >>http://cygwin.com/problems.html > >Here it is. To quote from that page: # Run cygcheck -s -v -r > cygcheck.out and include that file as an attachment in your report. Please do not compress or otherwise encode the output. Just *attach it* as a *straight text file* so that it can be easily viewed. cgf >begin 666 cygcheck.out >M#0I#>6=W:6X AT 0V]N9FEG=7)A=&EO;B!$:6%G;F]S=&ECM>7-T96T AT 5&EM93H AT 36]N($%P