Michael Back wrote: > I'm having a problem since I updated Cygwin early last week. When I start X > via startxwin.bat (which %RUN%'s an xterm), or run xterm from right-click on
[snip] I figured it out. When I located the recently moved startxwin.bat script in /bin, and started it from that location, XTerm magically started receiving my keystrokes. Wish it were not so sensitive to the startup directory... Shortcut to startxwin properties: Target: C:\cygwin\bin\startxwin.bat Start in: C:\cygwin\bin > The XTerm seems also to be ignoring my .Xdefaults file. I'm still having problems with Xdefaults -- can't yet get XTerm to respond to the following: XTerm.VT100.font: -*-bitstream vera sans mono-medium-*-r-*-16-*-*-*-*-*-*-* XTerm.VT100.boldFont: -*-bitstrean vera sans mono-bold-*-r-*-16-*-*-*-*-*-*-* XTerm.VT100.background: Black XTerm.VT100.foreground: Gray XTerm.cursorColor: Green The terminal remains black characters on a white background. Thanks, Michael -- 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/