On Mon, Dec 1, 2014 at 3:32 PM, Mark Hansen <[email protected]> wrote: > On 12/1/2014 8:35 AM, Tim Kingman wrote: >> >> *snip* >> my .bashrc calls startxwin >> to make sure I always have an X server running ( per >> http://stackoverflow.com/a/9301966 ) >> *snip* >> >> I'll keep playing with this to see if I can come up with a solution to >> duplicate my previous behavior: Any new bash shell makes sure that X >> is running, with no X apps running, and only one X is running, and new >> shells don't pop up any "display already exists" errors. >> >> Thanks, >> Tim >> > > Tim, > > Are you opposed to having the X Server start when you log into the Windows > machine? > This is what I do and it works well. The X server is always running when I > need it. > > I created a desktop shortcut with the following command: > > C:\Apps\cygwin\bin\run.exe /usr/bin/bash.exe -l -c "/usr/bin/startxwin.exe > -- -emulate3buttons 100 -multiwindow -clipboard -swcursor" > > and then just place that shortcut in the "programs -> startup" start menu > folder. >
Mark, That's probably what I should be doing to start the X server. That would avoid the dup-error warnings, and I can manually restart the server if it dies. But I think this method won't work with xinit 1.3.4, because startxwin.bat from xinit 1.3.4 no longer leaves the X server running after the last command in .startxwinrc (or the default xterm) exits. Another request for this: https://cygwin.com/ml/cygwin-xfree/2014-11/msg00039.html with a suggestion to run sleep from .startxwinrc. I haven't tried that yet, but that may be the best option for now. Thanks, Tim -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
