> -----Original Message----- > From: Marco Atzeri [mailto:marco.atz...@gmail.com] > Sent: Tuesday, December 23, 2014 2:17 PM > To: cygwin-xfree@cygwin.com > Subject: Re: Need help to replicate old behavior of my X setup scripts with > latest Xfree86 update > > > > > try putting "sleep inf" in .startxwinrc > It should simulate the old behaviour > > Regards
Thanks for the suggestion. I actually figured out something similar. I launched fbpanel instead with this command: exec /usr/bin/fbpanel -p multiwindow I also discovered that the X server is not always opened on display 0, which I wanted to force, so I did some digging and found I can do that by creating a ~/.xserverrc file to change how it launches the X server. I put this in the file instead: /usr/bin/XWin :0 -multiwindow -nolisten tcp I don’t need external connections as I’m primarily using the X server for local programs or with ssh -Y, so the nolisten switch works fine for me. I also didn’t want xterm to start up at launch, so I had to create an empty ~/.Xclients file. Finally, I had change my startup script so that, if the X server isn't running yet, it would launch startxwin in the background and loop until it sees the fbpanel process in the process list, or time out (after 30 seconds). If it sees the process start, it sets up my configurations as before. It works, albeit not as cleanly as before. I get the extra icon in my taskbar for fbpanel since it’s running, and I see the job number get echoed out to the terminal when it backgrounds the startxwin script. It also takes longer to start since I’m launching fbpanel on top of the server, though I suppose putting the sleep command would alleviate some of that. I’ll look into it. Thanks! Sincerely, Benjamin Richards -- 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/
