I just installed LyX 1.3.5 as part of an upgrade of KDE; the LyX was actually listed in the KDE installer tool, Konstruct, which downloads various bits of source and configs and compiles them.
I had been using LyX 1.3.2 with Qt 2.x successfully, and so far the new LyX seems to work, except for the lack of any Meta capability. My Xmodmap has the Alt key mapped to Meta_L, and that has not changed. xkeycaps shows the appropriate keycodes for all the keys. LyX is the only app I use that knows about Meta, so I don't have anything to compare against, except the fact that LyX 1.3.2 worked. My most basic testing has been to try to throw the focus to the minibuffer with M-x, on the theory that that test should bypass any bind file peculiarities, changes in syntax there between LyX versions, etc. My bind file contains: \bind "M-x" "command-execute" which seems about as simple as it gets. Nothing works; I don't get an "Unknown function" complaint, I just get an "x" in the text of my document, as though the Meta key wasn't there. But according to xmodmap it is, indeed, there: $: xmodmap -v -pm ! ! executing work queue ! xmodmap: up to 3 keys per modifier, (keycodes in parentheses): shift Shift_L (0x32), Shift_R (0x3e) lock Caps_Lock (0x42) control Control_L (0x25) mod1 Meta_L (0x40), Alt_L (0x7d), Meta_L (0x9c) I've tried <ESC> as well as the Alt key, with the same result. I have LYX_DIR_13x and LYX_USERDIR_13x set correctly. The KDE build tool takes the LyX source from ftp://ftp.lyx.org/pub/lyx/stable/ Is there a known issue with this version of LyX and/or Qt? Is there something else I need to configure? Can someone suggest any debug strategy? TIA, Jim
