This is the mail archive of the
mailing list for the GCC project.
Re: Problem with pex-win32.c
- From: Paul Brook <paul at codesourcery dot com>
- To: gcc at gcc dot gnu dot org
- Cc: "Dave Korn" <dave dot korn at artimi dot com>, "'Ross Ridge'" <rridge at csclub dot uwaterloo dot ca>
- Date: Tue, 14 Mar 2006 19:21:50 +0000
- Subject: Re: Problem with pex-win32.c
- References: <000d01c6479a$3e2e8690$a501a8c0@CAM.ARTIMI.COM>
> > Is this really worth it? Could this whole problem be solved by you
> > switching to rxvt? Maybe the only problem is that your xterm is broken.
> Nothing is "broken". The problem is that Cygwin applications run in a
> slightly special environment, where there may not be a console attached to
> the shell window. This is not a problem for cygwin apps, but it can be for
> non-cygwin-aware apps launched from inside cygwin's 'special' environment
> that may assume that the standard win32 assumptions hold. This is a
> consequence of cygwin providing features over and above the underlying OS:
> software written for the underlying OS can't be aware of every possible OS
The problem isn't unique to cygwin. The same problems occur in any environment
that doesn't run inside a win32 console window. eg. most IDEs, including
Eclipse and MS Visual Studio.