On Mon, Dec 22, 2008 at 09:13:03PM -0500, Dan Espen despen-at-verizon.net |fvwm| wrote: > Chuck Martin <dclrk7...@sneakemail.com> writes: > > On Fri, Dec 19, 2008 at 08:25:24AM +0000, Thomas Adam > > thomas.adam22-at-gmail.com |fvwm| wrote: > >> 2008/12/19 Chuck Martin <dclrk7...@sneakemail.com>: > >> > Does anyone know why my keybindings fail when fvwm is run under xnest? > >> > I simply get an error for each binding that says "no such key". > >> > >> Depends on the binding -- because XNest acts as an XServer and an > >> XClient, getting FVWM that's running inside it to recognise modifier > >> keys correctly is problematic. If you look at using Xephyr instead, > >> that allows you to grab the pointer via CTRL + Shift which allows most > >> bindings to work for whatever is running under it. > > > > Could you be more specific? I've noticed that it works sometimes, but > > not always. In trying to find a pattern, every time I think I've figured > > it out, I find that I'm wrong. It seems to be completely random, but I > > suspect there must be a reason for it working sometimes, and if I could > > figure it out, I could make it work consistently (I say completely random, > > but it fails far more than it works). > > > > I should mention that I have remapped the keyboard quite a bit to add > > new modifier keys (Super, Hyper, and XF86Option, which are assigned to > > modifiers 3, 4, and 5, respectively) that are used exclusively for the > > window manager, and all of my FVWM key bindings use them. When the key > > bindings work, they *all* work, and when they don't they all fail. Any > > help would be greatly appreciated. > > Question 0.1 in the FAQ?
No. The bindings work in the main window manager, but not in the Xnested window manager. They also fail from the beginning, rather than after a few minutes. Before anyone says something about not being able to use the same bindings in an Xnested window manager as in the main window manager, I've configured FVWM to work a lot like vi, basically requiring very little use of the mouse, and that includes several modes, including a transparent mode in which all bindings are disabled except one, which allows me to reenable the key bindings. In transparent mode, the Xnested window manager should get all of the keys directly, and this only happens a very small percentage of the time. When it works it works until I close the window (or until it crashes, which Xnest has a tendency to do sometimes, but only when it isn't showing in the current viewport of the current desktop), but when it doesn't, it doesn't work from the start. I also mentioned that when the Xnested FVWM starts up, it shows a "no such key" error for every key binding attempted, which wouldn't happen if the problem was due to one of the *Lock keys was pressed. Chuck
