I know this thread is a bit old now but I just wanted to mention my
solution. I've added X to start in a separate screen in my
.bash_profile. That way every time I log into Cygwin, X is always available.
It's kind of like the previous suggestion of adding it to Windows
startup, but I have it
On 28/05/2014 13:57, Pavel Fedin wrote:
I believe this is arranged using launchd on OS X, which listens on the
socket the X server will use, and starts the X server when something
connects.
Unfortunately, there is no similar system facility on Windows.
But it should be possible to make xlib
Hello!
I believe this is arranged using launchd on OS X, which listens on the
socket the X server will use, and starts the X server when something
connects.
Unfortunately, there is no similar system facility on Windows.
But it should be possible to make xlib a little bit more smart,
Hello!
Recently i have started using Insight (https://sourceware.org/insight/)
under Cygwin/X. Everything is quite good except one thing.
I remember once upon a time i worked on MacOS X. There, X server starts up
automatically if there is some program requesting it. On Cygwin i still have
to
On 5/27/2014 8:52 AM, Pavel Fedin wrote:
Hello!
Recently i have started using Insight (https://sourceware.org/insight/)
under Cygwin/X. Everything is quite good except one thing.
I remember once upon a time i worked on MacOS X. There, X server starts up
automatically if there is some
On 27/05/2014 13:52, Pavel Fedin wrote:
Recently i have started using Insight (https://sourceware.org/insight/)
under Cygwin/X. Everything is quite good except one thing.
I remember once upon a time i worked on MacOS X. There, X server starts up
automatically if there is some program
