On 04.10.2011 21:24, David Palacio wrote:
> On Tue, Oct 04, 2011 at 08:28:39PM +0200, Uli Schlachter wrote:
>> Pushed, although I'm still not convinced.
>>
>> Wouldn't something like this solve the problem in a cleaner way?
>>
>> diff --git a/awesomerc.lua.in b/awesomerc.lua.in
>> index fcfb333..ef8cc96 100644
>> --- a/awesomerc.lua.in
>> +++ b/awesomerc.lua.in
>> @@ -306,6 +306,8 @@ awful.rules.rules = {
>> focus = true,
>> keys = clientkeys,
>> buttons = clientbuttons } },
>> + { rule = { type = "desktop" },
>> + properties = { skip_taskbar = true } },
>> { rule = { class = "MPlayer" },
>> properties = { floating = true } },
>> { rule = { class = "pinentry" },
>>
>
> I recompiled Awesome with patch 0001 and without patch 0002 from my previous
> mail. Then I added this rule to the relevant window class. It does not make
> a difference in the taglist widget.
Oh, taglist. I guess that should be solved via a taglist filter then. E.g.
instead of filter.noempty, it would need an own function which skips clients
with skip_taskbar... Or so.
> It also has the side effect that it untags the client from all tags but one.
Weird. No idea. :(
> This is the rule I use:
>
> { rule = {
> instance = "luaplasma",
> -- with skip_taskbar set to either true or false
> -- the tags set below in the callback are unset for
> -- the client
> properties = { skip_taskbar = true }
> },
> callback = function(c)
> c:tags({
> tags[c.screen][1],
> tags[c.screen][2],
> tags[c.screen][3],
> tags[c.screen][4],
> tags[c.screen][8]
> })
> end },
--
Q: Because it reverses the logical flow of conversation.
A: Why is putting a reply at the top of the message frowned upon?
--
To unsubscribe, send mail to [email protected].
