>>>>> "DRE" == D R Evans <[EMAIL PROTECTED]> writes:

    DRE> I've seen a few references in the archives to running xemacs
    DRE> over VNC connections, but nothing that mentions the problem
    DRE> that I am seeing.

    DRE> When I run VNC (Win98 client; Linux server) and fire up
    DRE> xemacs on the server, I see four keymap warnings. These
    DRE> warnings take up the bottom half of the editing frame and are
    DRE> rather annoying.

    DRE> Anyone have any idea how I can make them go away?

The problem is that Xvnc assigns both META and ALT key to the same X
modifier. I don't like this behaviour and agree with XEmacs on this
issue (I always use different keys for ALT and META), that is why I've
changed such behaviour in TightVNC (http://www.tightvnc.com/) where I
assign these keys to different modifiers. So you might want to try
TightVNC which should solve the problem.

Here is the patch in case if somebody wants to solve this problem in
standard VNC:

=== cut ===
Index: vnc_unixsrc/Xvnc/programs/Xserver/hw/vnc/kbdptr.c
diff -u vnc_unixsrc/Xvnc/programs/Xserver/hw/vnc/kbdptr.c:1.2 
vnc_unixsrc/Xvnc/programs/Xserver/hw/vnc/kbdptr.c:1.3
--- vnc_unixsrc/Xvnc/programs/Xserver/hw/vnc/kbdptr.c:1.2       Fri Oct 27 03:19:19 
2000
+++ vnc_unixsrc/Xvnc/programs/Xserver/hw/vnc/kbdptr.c   Tue Oct 31 16:20:25 2000
@@ -192,8 +192,8 @@
     pModMap[CONTROL_R_KEY_CODE] = ControlMask;
     pModMap[SHIFT_L_KEY_CODE] = ShiftMask;
     pModMap[SHIFT_R_KEY_CODE] = ShiftMask;
-    pModMap[META_L_KEY_CODE] = Mod1Mask;
-    pModMap[META_R_KEY_CODE] = Mod1Mask;
+    pModMap[META_L_KEY_CODE] = Mod4Mask;
+    pModMap[META_R_KEY_CODE] = Mod4Mask;
     pModMap[ALT_L_KEY_CODE] = Mod1Mask;
     pModMap[ALT_R_KEY_CODE] = Mod1Mask;
 
=== cut ===

-- 
With Best Wishes,
Constantin
---------------------------------------------------------------------
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
---------------------------------------------------------------------

Reply via email to