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/
