X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: Lewis Hyatt <lhyatt AT princeton DOT edu>
Subject:  Re: using chere
Date:  Wed, 20 Jun 2007 16:05:44 -0400
Lines: 49
Message-ID: <f5c1ap$opv$1@sea.gmane.org>
References:  <46796B90 DOT 3 AT princeton DOT edu> <46797188 DOT 3050501 AT gmail DOT com> <f5bs7g$5n1$1 AT sea DOT gmane DOT org> <46798085 DOT 5060608 AT gmail DOT com>
Mime-Version:  1.0
Content-Type:  text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding:  7bit
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
In-Reply-To: <46798085.5060608@gmail.com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

Dave wrote:

> At a guess, do you need to make sure the DISPLAY environment variable is
> set for the xterm to find the server? You have it set in your cygcheck
> output, but you clearly produced that within an xterm which will have
> the variable set.
> 
> If that's the case DISPLAY will need to be set in the users Windows
> environment for chere to start xterms.

DISPLAY is set in the Windows environment as well; cygwin must have done 
this for me, since I didn't do it manually.

I did some more digging, and here is what I find. If I start bash from a 
Windows CMD prompt by simply typing:

	cd \cygwin\bin
	bash

And then I type:

	./xterm

bash does not complain, because it finds xterm.exe in the current 
directory, but the xterm fails to pop up.

On the other hand, if I start bash as follows:

	cd \cygwin\bin
	bash --login -i

And then I type:

	./xterm

then the xterm pops up as expected.

The difference is that --login -i directs bash eventually to read 
/etc/profile, which adds cygwin dirs to the path. So as Morgan thought, 
this is somehow a PATH issue. However, I added c:\cygwin\bin, 
c:\cygwin\user\X11R6\bin to my Windows path, and the chere still does 
not pop up an xterm. (Note that adding these dirs to the Windows path is 
not an option for me anyway, as it causes me a lot of DLL-hell type 
problems).

Do you have any more suggestions what I could try? Thanks again for your 
assistance!

-Lewis


--
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/