New X server
Hi. I appreciate the work you guys do for Cygwin, but I just got blasted with the new xorg-server update when I was just trying to grab another package. I say "blasted" because it was not a good thing. Where I used to be able to lay out nice, clean terminal windows across my Windows desktop, I now have a single, monolithic, unresizable "Cygwin/X:0.0" window that seems to have a few terminal windows in it and nothing else. These terminal windows are anything but nice and clean, like the previous ones were. They're not resizable, either, and also unmovable. They have clunky menu bars at the top, and some of them overflow the bottom of the Cygwin/X window that they're in, and there's no way to move down and see the overflow. All in all, the update completely broke X for me. What do I need to do to get it usable? I've already read this: http://cygwin.com/ml/cygwin-xfree-announce/2008-11/msg0.html It's not any help. -- 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/
Alias problem with bash -l (was Re: New X server)
Jon TURNEY wrote: [...] > It sounds like you have somehow lost "-multiwindow" from the command used to > start the X server (so the server is operating in the default, windowed mode). [...] > Run xterm +tb, or add "XTerm*toolBar: false" to ~/.Xdefaults Awesome! Those were exactly what I was looking for, and I also learned a few other things along the way. Thanks so much. I'm having one other problem now, though, which might be a bug. When bash is started with the "-l" (that's an 'L') flag, aliases that I've defined in .bashrc don't take effect. My .bash_profile includes a call to .bashrc, and I know that .bashrc is being executed because I've put an echo at the beginning and end of it, and both messages are printed out. Even if I execute .bashrc manually, it will print out the messages, but I get no aliases. I can, however, manually enter aliases, and they work. -- 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/
Re: Alias problem with bash -l (was Re: New X server)
Christopher Faylor wrote: > On Thu, Nov 20, 2008 at 12:37:51PM -0600, Ryan Stewart wrote: [...] > I doubt that the base maintainer would be scanning the cygwin-xfree > mailing list looking for problem reports. > > Please use the cygwin list for non-x-related problems. > > cgf Sorry about that. I'm new to cygwin and wasn't thinking about the difference. -- 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/
can't start xterm
Yet again, I seem to have inadvertently gotten an update to cygwin X, and now I'm having trouble getting xterm to start. 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. Same deal if I run "XWin.exe" or "XWin -multiwindow" manually. If I run Cygwin.bat to get the cygwin shell, then run startx, I get the "Cygwin/X:0.0" blue root window with a "login" xterm and various, square "icon" things in three of the corners. I'm not sure exactly what this is, but it's the only place that I can currently get new xterm windows to open, either by using Applications->xterm from the tray icon or by running "xterm" from the existing terminal. How can I get back to running X in multiwindow mode so I can have several xterm windows? -- 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/
Re: can't start xterm
On Thu, Feb 5, 2009 at 9:59 PM, Dan Moulding wrote: > > On Feb 5, 2009, at 2:30 PM, Ryan Stewart 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/
Re: can't start xterm
>> > On Feb 5, 2009, at 2:30 PM, Ryan Stewart 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 >> Problem solved by using the startxwin.bat in /usr/X11R6/bin. I guess the one at /usr/bin wasn't updated because I'd modified it? The only change I noticed was from: SET RUN=%CYGWIN_ROOT%\bin\run -p /usr/bin to: SET RUN=%CYGWIN_ROOT%\bin\run -p /usr/X11R6/bin This strikes me as odd, since the upgrade instructions seem to indicate that /usr/X11R6/bin was going away in favor of /usr/bin: http://cygwin.com/ml/cygwin-xfree-announce/2008-11/msg0.html So what's the deal here? Where is startxwin.bat supposed to live now? And how do I overcome the apparent problem of customizing it and getting killed by updates? A separate question: where can I find some documentation on \cygwin\bin\run.exe? I only have a vague idea what it does and no idea what options are available with it. -- 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/
