> >
> > How does the location of the startup batch file affect the behavior of
> > numlock and capslock in xterm?
> >
> Yes. The batch file is different. The binary is different. The
> environment variables are different. For example this is in the old
> batch file but not in the new one.
> SET XAPPLRESDIR=/usr/X11R6/lib/X11/app-defaults
> SET XCMSDB=/usr/X11R6/lib/X11/Xcms.txt
> SET XKEYSYMDB=/usr/X11R6/lib/X11/XKeysymDB
> SET XNLSPATH=/usr/X11R6/lib/X11/locale
> I suspect that XKEYSYMDB one has something to do with the problem you're
> having. The new file doesn't assign these variables at all, and runs a
> different binary.

I just re-installed Cygwin on my machine, deleted my .bash_profile,
.bashrc and .Xdefaults in my home, and I still have the same
numlock/capslock issue.

My config is quite standard : Windows XP SP2. It is easily
reproductible I guess.

BTW, in startxwin.bat, this line :
is true only if you install Cygwin in the default path. I had to
change it to match my configuration, otherwise the "XWin Server" does
not 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/

Reply via email to