> vicious.cache(vicious.widgets.volume)
Remove it.
--
Adrian C. (anrxc) | anrxc..sysphere.org | PGP ID: D20A0618
PGP FP: 02A5 628A D8EE 2A93 996E 929F D5CB 31B7 D20A 0618
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Hi Guys,
could anyone of you give me a hint how to get Shifty to re-check the
windows titles when they change?
I got a bunch of terminals at work, all going to some gateway-hosts and
from there to a really big multiverse of landscapes of servers.. ;)
Now I end up with exactly one tag with all my
On Fri, Feb 17, 2012 at 1:30 AM, Derek Thurn wrote:
> That works unless I have multiple Chrome windows, which is why I
> thought about absolute positioning.
function next_client(property)
local clients = client.get()
local start= awful.util.table.hasitem(clients, client.focus)
local i
That works unless I have multiple Chrome windows, which is why I
thought about absolute positioning.
On Thu, Feb 16, 2012 at 1:54 AM, Anurag Priyam wrote:
> On Thu, Feb 16, 2012 at 5:20 AM, Derek Thurn wrote:
>> The motivation behind this is that I want a keyboard shortcut that
>> does something
> You forgot to CC the list :).
Indeed, sorry :)
> Doesn't `-name` option of urxvt help? For a terminal launched as:
>
> $ urxvt -name foo
>
> you can match it in awesome with:
>
> { rule = { instance = "foo" },
> ...
> }
Yes, this probably could make it! I totally forgot about -name :)
>> Op
[+CC: awesome@naquadah.org]
You forgot to CC the list :).
On Thu, Feb 16, 2012 at 11:35 PM, Paweł Rumian wrote:
> Thank you very much for your solution Anurag - unfortunately it's not
> THAT easy.
> Saying about 'terminal' was an unnecessary simplification made by me -
> in fact it is a monitori
On Thu, Feb 16, 2012 at 10:25 PM, Paweł Rumian wrote:
> is it possible to place application to a specific tag of specific
> screen when autostarting, but not making it permanent for all similar
> applications?
You can probably do this using a callbacks in rules:
> E.g. I want to open terminal at
Shifty can start a client on a specific tag.
http://awesome.naquadah.org/wiki/Shifty
2012/2/16 Claudio Roberto França Pereira :
> It would be great if the run command widget also remembered the
> current tag to spawn the next window there. Sometimes Firefox takes
> some seconds to spawn, so I spaw
It would be great if the run command widget also remembered the
current tag to spawn the next window there. Sometimes Firefox takes
some seconds to spawn, so I spawn it then go to another tag, just to
have it flood my other tag.
--
Claudio Roberto França Pereira
On Thu, Feb 16, 2012 at 15:04, A
On Thu, Feb 16, 2012 at 10:25 PM, Paweł Rumian wrote:
> is it possible to place application to a specific tag of specific
> screen when autostarting, but not making it permanent for all similar
> applications?
> E.g. I want to open terminal at tag 4 of screen 2, but obviously
> auto-putting ALL fu
Hello,
is it possible to place application to a specific tag of specific
screen when autostarting, but not making it permanent for all similar
applications?
E.g. I want to open terminal at tag 4 of screen 2, but obviously
auto-putting ALL further terminal windows there makes no sense.
I currently
On Thu, Feb 16, 2012 at 5:20 AM, Derek Thurn wrote:
> The motivation behind this is that I want a keyboard shortcut that
> does something like "always switch to this chrome window, regardless
> of which client and screen currently has focus". I figure I could just
> make sure the right chrome wind
On 16.02.2012 00:50, Derek Thurn wrote:
The awful.client API specifies focus.byidx, which lets you switch
focus to a client by its relative index. What I want is to switch to a
client by *absolute* index. Is that possible?
The motivation behind this is that I want a keyboard shortcut that
does s
The awful.client API specifies focus.byidx, which lets you switch
focus to a client by its relative index. What I want is to switch to a
client by *absolute* index. Is that possible?
The motivation behind this is that I want a keyboard shortcut that
does something like "always switch to this chrom
On 02/16/12 12:18, Alexander Yakushev wrote:
Is your awesome capable of displaying JPG images at all? Try it by
executing:
notify-send "test" "test" --icon=/path/to/any/jpg/file.jpg
If no image is displayed, then either update your awesome to 3.4.11
release (Pickapart) or compile the lates
Is your awesome capable of displaying JPG images at all? Try it by
executing:
notify-send "test" "test" --icon=/path/to/any/jpg/file.jpg
If no image is displayed, then either update your awesome to 3.4.11
release (Pickapart) or compile the latest version from git repository if
you prefer t
Hello!
I tried using scripts on the
https://awesome.naquadah.org/wiki/Coverart_display web-page but I see
empty notification. Why is it so?
Awesome: 3.4.11-186-g55f3ace
Kernel: 3.2.0-1-amd64 on Linux Debian testing
Thanks in advance!
--
To unsubscribe, send mail to awesome-unsubscr...@naqua
17 matches
Mail list logo
