On Thu, Sep 17, 2020 at 11:02:11AM -0400, Conrad Knight wrote: > I posted to this list on 18th July about E 0.24 breaking xmodmap > (possibly, i was looking for confirmation and a fix). Could whatever > changed to break xkb also be affecting xmodmap? > > The tl;dr version of that message is: > Compose key still works (separately set by X), but > xmodmap -e "keycode 133 = Multi_key dead_greek" > has no effect any more, shift-compose does nothing. Still works with > other WMs, or none at all, only broken in E.
I had been using xmodmap for 20 years or so, but Xorg definitely broke it enough that I had to switch to xkbmap. Some links I wrote down I went through that process https://unix.stackexchange.com/questions/202883/create-xkb-configuration-from-xmodmap http://madduck.net/docs/extending-xkb/ https://wiki.archlinux.org/index.php/X_KeyBoard_extension https://stackoverflow.com/questions/7799071/use-xkbdmap-setxkbmap-to-map-rwin-to-altgr https://wiki.archlinux.org/index.php/Keyboard_configuration_in_Xorg https://zuttobenkyou.wordpress.com/2011/08/24/xorg-using-the-us-international-altgr-intl-variant-keyboard-layout/ Hope this helps :) Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Home page: http://marc.merlins.org/ | PGP 7F55D5F27AAF9D08 _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
