On Thu, Feb 5, 2009 at 9:59 PM, Dan Moulding <dmoulding at gmail dot com> wrote: > > On Feb 5, 2009, at 2:30 PM, Ryan Stewart <rds6...@gmail.com> wrote: > > > > I had been using > > the startxwin.bat to start X in multiwindow mode, and I have a couple > > of lines in there to auto-start some xterm windows. That doesn't work > > anymore. The X server starts, but no xterms appear. When I right click > > the tray icon and go to Applications->xterm, nothing happens either > > What happens if you run xterm from a bash shell started from Cygwin.bat? > I'm thinking it might give you an error message that may hint at the > cause of the problem. > Interesting. Restarting the computer seems to have made some difference. I can now start xterm normally in every case except when I start X using startxwin.bat. When I start it that way, I *can* start xterm from a separate bash shell, as you suggested--and there are no errors--but I still can't start it using the tray icon, and the xterms I've set up to start in startxwin.bat don't start, either. Those xterms in the batch file are my main concern.
The batch file starts X like this: %RUN% XWin -multiwindow -clipboard -silent-dup-error where RUN=\cygwin\bin\run -p /usr/bin Then I have lines like this: %RUN% xterm %RUN% xterm -e /usr/bin/bash -l Neither of them work, but starting a cygwin shell and running the corresponding command from there, i.e. without the %RUN% in front, does work. These commands worked before I got an unrequested update yesterday. -- 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/