xemacs and xmodmap

Hello,

my xemacs is just too intelligent ;)
I set up my .Xmodmap so that "Caps Lock" ( the most senseless key on the 
board ) creates "mod4". This way I can controll my all of my fvwm2 
functions with this key and don't mess up other key sequences. I think 
this makes sense, but xemacs disagrees:

(1) (key-mapping/warning) 
        The meanings of the modifier bits Mod1 through Mod5 are determined
        by the keysyms used to control those bits.  Mod1 does NOT always
        mean Meta, although some non-ICCCM-compliant programs assume that.

(2) (key-mapping/warning) 
        The semantics of the modifier bits ModShift, ModLock, and 
ModControl
        are predefined.  It does not make sense to assign ModControl to 
any
        keysym other than Control_L or Control_R, or to assign any 
modifier
        bits to the "control" keysyms other than ModControl.  You can't
        turn a "control" key into a "meta" key (or vice versa) by simply
        assigning the key a different modifier bit.  You must also make 
that
        key generate an appropriate keysym (Control_L, Meta_L, etc).

(3) (key-mapping/warning) XEmacs:  Caps_Lock (0x42) generates Mod4, which 
is nonsensical.


How can i get rid of these warnings ?

My .Xmodmap contains only:

remove Lock      = Caps_Lock
add Mod4 = Caps_Lock
keycode 101 = Multi_key

Thanks,

Markus Grunwald
Softwareentwicklung

PRÜFTECHNIK Condition Monitoring GmbH
Oskar-Messter-Straße 19-21
85737 Ismaning
www.pruftechnik.com
Tel: +49 (0)89 99616177
Fax: +49 (0)89 99616200