On 05/02/13 07:11:11 +0000, Daniel wrote:
> On Tue, Feb 05, 2013 at 05:19:09PM +0000, Ignas Anikevičius wrote:
> > What is wrong in removing the definition in globalkeys and leaving
> > only
> > the clientkey one?
> >
> > Also, this does not happen a the key bindings are managed via signals,
> > which means that the same signal (i.e. a key press) triggers two
> > different function definitions... If I am wrong maybe someone else
> > would
> > be able to describe what happens better.
>
> Labas! You missed the mailinglist by a char ;)
>
> Well, the idea was to sometimes override the globalkey. For example,
> a global key for closing/killing the client that shouldn't work on certain
> clients. But I guess I could have a global key that takes a look on the
> client and decides whether to close it or not.
Labas... :)
Why not do something like that:
clientkeys = my usual definition of client keys except the kill function
clientkeys_kill = my kill key function
awful.rules.rules = {
{ rule = { },
properties = { border_width = beautiful.border_width,
border_color = beautiful.border_normal,
keys = awful.util.table.join(clientkeys,clientkeys_kill)
focus = awful.client.focus.filter,
size_hints_honor = false,
buttons = clientbuttons,
}
},
{ rule_any = { The exceptions },
properties = { keys = clientkeys }
},
...
}
This approach should work, or, at least, I have no idea why it
wouldn't...
Cheers,
Ignas
--
To unsubscribe, send mail to [email protected].
