I just started using the VNC server for X, and the WinVNC viewer. It
worked fine, except whenever I pressed the Backspace key, nothing
happened. I investigated a little, and found that I'd set things up
so that, whenever *any* X server started, I'd run "xmodmap", and
configure the X server in ways that were appropriate for a Microsoft
Natural keyboard (which indeed is what's connected to the Unix
computer), but not for the VNC server's virtual keyboard.
So to fix the problem, I ran "xev" to find that the Backspace key was
sending keycode 64, and then I wrote the following little shell
script, which I've arranged to run whenever *any* X server starts:
#!/bin/sh
xserver_vendor=$(xdpyinfo | egrep -i 'vendor string')
case $xserver_vendor in
*AT\&T*)
xmodmap -e "keycode 64 = BackSpace"
;;
*)
xmodmap $HOME/.xmodmap-$(uname -n)
;;
esac
I suggest that the VNC documentation (perhaps the "Getting Started"
web page), or the vncserver script itself, contain a warning something
like this:
If you find that key-presses aren't doing what you expect, you may
need to fiddle with "xmodmap". In particular, make sure you're
not using xmodmap to configure the X server in a way that assumes
you're using a particular physical keyboard. See http://something
for details.
(http://something could point to one of the VNC web pages; it could
contain this message.)
That would save time for people like me.
Ultimately, someone should teach the nifty XKeyCaps program about the
VNC server for X, so that we could easily generate a complete set of
xmodmap input. I'll look into that.
--
The best things in life are non-proprietary.
PGP Fingerprint: 3E7B A3F3 96CA 8958 ACC5 C8BD 6337 0041 C01C 5276
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
