This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Problem with pex-win32.c


> > 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
> extension.

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.

Paul


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]