Re: Incorrect key binding handling for `similar' bindings defined for different window types
Tuomo Valkonen <tuomov@...
2005-06-08 19:35:34 GMT
On 2005-06-08, Jeremy Maitin-Shepard <jbms@...> wrote:
> Tuomo Valkonen <tuomov@...> writes:
>> On 2005-05-31, Jeremy Maitin-Shepard <jbms@...> wrote:
>>> When I press "Mod4+K" followed by "Mod4+n", WFrame.switch_next is
>>> called, rather than ionws_move_current.
>> That's how it should work.
> Please explain why. Note that the switch_next command is bound to
> "Mod4+K n"; the ionws_move_current command is bound to "Mod4+K Mod4+n".
> Thus, when I type "Mod4+K Mod4+n", I expect the ionws_move_current
> command to be triggered, rather than the switch_next command.
Submaps default to "AnyModifier" pseudo-modifier and thus catch anything.
Since the frame is inside the workspace in the region hierarchy, the frame
bindmap has precedence over the workspace bindmap, and this binding gets
called. If you want only "n" with no modifiers set be catched, use