Ok I read again my previous answer, and understood it was not clear.
Le 31/10/2013 23:13, Michael Hauser a écrit :
Hi,
Hi (sorry I forgot to say "Hi" in my previous answer.
quick question: why the distinction between global and client keys and
how to unify?
Because client keys are attached to each client (hence the client
parameter "c"), let say "are duplicated for each client", and global
ones do not.
Perhaps I just don't see how to adress a focused client with global key
bindings?
Clientkeys are associated to each client in the rules (from default
config) :
> awful.rules.rules = {
> -- All clients will match this rule.
> { rule = { },
> properties = { border_width = beautiful.border_width,
> border_color = beautiful.border_normal,
> focus = awful.client.focus.filter,
> keys = clientkeys,
> buttons = clientbuttons } },
> { rule = { class = "MPlayer" },
> properties = { floating = true } },
> { rule = { class = "pinentry" },
> properties = { floating = true } },
> { rule = { class = "gimp" },
> properties = { floating = true } },
> -- Set Firefox to always map on tags number 2 of screen 1.
> -- { rule = { class = "Firefox" },
> -- properties = { tag = tags[1][2] } },
> }
I don't know awesome code, but I'm guessing that the client parameter is
given to the client keys thanks to this mapping. Also, unifying global
and client keys has no meanig, you might have missunderstood something,
did you?
I'm in the process of implementing a modal UI (vim like) and don't want
the need of a second key, if no client is on the screen…
Maybe you can develop your question, what do you want?
I bet on run or raise functionnality
<http://awesome.naquadah.org/wiki/Run_or_raise> :)
BTW, awesome rocks!
cheers, mih
Vlamy.
