After upgrading to XDarwin 18.104.22.168, Option/F3 (for
instance) fails to lower window in the Motif-like
manner (using IceWM in this case).
Logged In: YES
The new keyboard mapping code does use the option key to get the 3rd and 4th character. This should work as it does in MacOS. To enable the switch to the new levels, the option key had to be mapped to Mode_switch.
You could try to use the Apple key (which is mapped to Meta) instead of Alt.
The man-page of xmodmap mentions, that you can create a mapping, that produces more than one keysym for a given key. Perhaps this is a way to solve this problem.
Here a section from the xmodmap man page:
Many applications support the notion of Meta keys (similar to Control keys except that Meta is held down instead of Control). However, some servers do not have a Meta keysym in the default keymap table, so one needs to be added by hand. The following command will attach Meta to the Multi-language key (sometimes labeled Compose Character). It also takes advantage of the fact that applications that need a Meta key simply need to get the keycode and don't require the keysym to be in the first column of the keymap table. This means that applications that are looking for a Multi_key (including the default modifier map) won't notice any change.
% xmodmap -e "keysym Multi_key = Multi_key Meta_L"
Similarly, some keyboards have an Alt key but no Meta key. In that case the following may be useful:
% xmodmap -e "keysym Alt_L = Meta_L Alt_L"
Logged In: NO
The symptoms are more widespread:
1. In full screen mode, cmd-opt-a does not respond.
2. When trying to change from cmd-opt-a to something else in
XDarwin's preferences dialog, no key combinations are
accepted and the button stays stuck at "Press Key" until one
clicks on "Cancel."
3. WindowMaker shortcuts don't work at all (switching
workspaces, toggling among windows). Bringing up the
preferences dialog to change the key mappings does recognize
meta (command) but not option.
It's even worse - I had to back up to the previous XDarwin
version. In emacs I cannot even type an "at sign". I *think*
it comes out as a single quote. Very strange ...
Torrey T. Lyons
Logged In: YES
A lot of bugs have gotten intermixed here. The original bug report, that Alt/Option does not work as expected for many poeple, has been fixed in XDarwin 1.0.5. The "@" character bug and others are described under other bug reports.
I still see the option-key-emulating-the-alt-key problem
in 22.214.171.124. Perhaps I need to cleanly de-install
XDarwind and do a fresh install?
Torrey T. Lyons
If you type "xmodmap" in XDarwin 1.0.5 you should see the following:
xmodmap: up to 2 keys per modifier, (keycodes in parentheses):
shift Shift_L (0x40), Shift_R (0x44)
lock Caps_Lock (0x41)
control Control_L (0x43), Control_R (0x46)
mod1 Mode_switch (0x42), Alt_R (0x45)
mod2 Meta_L (0x3f)
If you get this, then you XDarwin installation is fine. The question then is if there is a different configuration you want in your case. What happens by default is that Option produces Mode_switch and Mod1. If the X client you are using is looking for Mod1 and another key, then Option-<other key> will work as expected. If the X client is looking for the Alt_L keysym, then you won't be able to generate this with the default configuration. By default, Option has been set to generate special characters as it usually does in Mac OS. If you aren't interested in special characters and need Option to give you Alt_L you should change your keymap. The following command should do this for you:
xmodmap -e "keysym Mode_switch = Alt_L"