Uli Schlachter | 4 Jul 15:58 2015

Re: How to change mouse cursor size ?

Am 04.07.2015 um 19:26 schrieb Hacksign:
> added Xcursor.size: 64 in ~/.Xresources, but no any effect.

Is this applied?

Does xrdb -merge ~/.Xresources and then restarting awesome (ctrl-mod-r in the
default config) help?

> BTW:
> icon also too small any way make it larger ?

Dunno, I don't know much about GTK theming.

Who needs a ~/.signature anyway?

Johannes Sauer | 11 Jun 16:21 2015

Howto apply certain rules only at startup


what I want to do is automatically start application on a certain tag. However when I later start another instance of the application I want it to appear on the tag I am at that moment.
I tried to do something like this in rc.lua:

   rules_always  = {
       -- All clients will match this rule.
       { rule = { },
         properties = { border_width = beautiful.border_width,
                        border_color = beautiful.border_normal,
                        focus = true,
                        keys = clientkeys,
                        buttons = clientbuttons } },
       -- Set Thunderbird to always map on tags number 3 of screen 1.
       { rule = { class = "Thunderbird" },
         properties = { tag = tags[1][3] } },
   rules_startup = {
       -- Set Firefox to always map on tags number 3 of screen 1.
       { rule = { class = "Firefox" },
         properties = { tag = tags[1][2] } },
   awful.rules.rules = awful.util.table.join(rules_always, rules_startup)

then at the end of rc.lua:


   awful.rules.rules = rules_startup

However the effect is that still all rules will be applied, i.e. every new instance of firefox will appear on tag 2.

What am I doing wrong?


PS: My awesome version is 3.4.11, don't think it's relevant for this question.

Elv1313 . | 5 Jun 23:04 2015

Fwd: Dual-Monitor Systray

I don't think so, it require the compositor to be tied to the shell
and a lot of hacky code. XEMBED is a terrible thing, a security
nightmare and is also totally inflexible (no themes, *almost* no way
to have a transparent background, no accessibility support and so on).


On 5 June 2015 at 16:49, Jeferson Lesbao <jefersonlsiq <at> gmail.com> wrote:
> Hi,
> Didn't know about this X11 limitation. Using compton as an composite manager
> can make it possible ?
> Regards,
> Jeferson
> On Fri, Jun 5, 2015 at 5:47 PM, Elv1313 . <elv1313 <at> gmail.com> wrote:
>> Hello,
>> Not really, this is an X11 limitations, they simply forbid it by
>> design. Some WMs use compositing to "fix" this, but Awesome doesn't
>> have it's own compositor.
>> Regards,
>> Emmanuel
>> On 5 June 2015 at 16:43, Abraham Baker <z1693060 <at> students.niu.edu> wrote:
>> > Hi,
>> >
>> > Another multi-monitor question:  is it possible to have the system tray
>> > (where icons like nm-applet show up) appear on every monitor?
>> >
>> > I tried this and it now flickers unreliably between each monitor based
>> > on
>> > which client is focused:
>> >
>> > in rc.lua, around line 202:
>> >  right_layout:add(wibox.widget.systray())
>> >
>> > as opposed to
>> >   if s == 1 then right_layout:add(wibox.widget.systray()) end
>> >
>> > Thanks,
>> > Abe
>> --
>> To unsubscribe, send mail to awesome-unsubscribe <at> naquadah.org.

Abraham Baker | 5 Jun 22:43 2015

Dual-Monitor Systray


Another multi-monitor question:  is it possible to have the system tray (where icons like nm-applet show up) appear on every monitor?

I tried this and it now flickers unreliably between each monitor based on which client is focused:

in rc.lua, around line 202:

as opposed to
  if s == 1 then right_layout:add(wibox.widget.systray()) end

John Yates | 3 Jun 18:08 2015

Trouble building on Debian 7 (wheezy)

I am trying to build the git tip.  Things seem to go fine until it is time to build the man pages:

Scanning dependencies of target lgi-check
[ 55%] Built target lgi-check
Scanning dependencies of target man
[ 56%] Generating manpages/man1/awesome.1.xml
[ 57%] Generating manpages/man1/awesome.1
Note: Writing awesome.1
make[3]: *** [manpages/man1/awesome.1] Error 1
make[2]: *** [CMakeFiles/man.dir/all] Error 2
make[1]: *** [all] Error 2
make: *** [install] Error 2

Any suggestions?

Abraham Baker | 3 Jun 15:12 2015

Naughty Notifications on multiple monitors


I have a standing/sitting monitor arrangement on my desk that makes it hard to see notifications on the upper monitor while sitting and vice versa.  I've been trying to change the default naughty config so notifications appear on both monitors at once, but so far I'm only able to just change which monitor it shows up on (not both).

Is there an easy way to have notifications shown on all monitors?

Abe Baker
mickael foucaux | 2 Jun 17:05 2015

advices for widget

Hi folks!

I'm happy with new laptop running an Ubuntu 14.01 / Awesome 3.5.6.

Now I'm looking for few useful / essentials widget as:
- battery state
- volume control
- wifi controller
- clock / calendar
- easy drive mounter

Ok I saw few of them in https://awesome.naquadah.org/wiki/User_Contributed_Widgets . However as I know not all of them are compatible with awesome 3.5.6, I would like some feedback and advice before to try randomly widgets.


Aleksander Szczygieł | 28 May 13:32 2015

Question about client.add_signal("custom_signal")


I have question - I need custom signal in my rc and I used undocumented 
function client.add_signal("custom_signal") (like it was made in 
awesoem/lib/awful/client.lua) to do it before using 
client.emit_signal("custom_signal"), but this function is undocumented so I'm 
not so sure if my way doing it is correct...

copied example from rc.lua:

-- add signal for toggling wibox on top (needed for forcing maximized clients 
globalkeys = awful.util.table.join(
awful.key({ modkey,           }, "b",
        function ()
            mywibox[mouse.screen].visible = not mywibox[mouse.screen].visible
        end, "Toggle panel"),
-- Connect toggle wibox signal to a resize function
client.connect_signal("wibox_toggle", reload_maximized_windows)

I'm not sure if this function should be used from user side (but it doesn't 
work without it) and I think if it function can be used it should be written 
in documentation.

dabicho | 26 May 23:58 2015

weird amd compton focus problem

I am using compton as a composite manager.

I starti it with --backend glx and then focus does not work correctly

I usually have to switch focus (press Mod+Tab) twice if the mouse
cursor is over the previous window.

Anyone has experienced the same problem? or a better alternative to compton?

Also, performance is not very good but I rather like being able to use
blured opacity.

Any hint.


Alexis BRENON | 25 May 17:19 2015

Re: Combination row+column layout?

Hi Rena,

Joined is a draft patch to add a "corner" layout. Of course, you have to add it in your rc.lua file!
You can also find it on my github account : https://github.com/AlexisBRENON/awesome/tree/feature/corner_layout
I compiled it without any problem and it works quite well. I've got some weird behaviour, but I tried it with small screen resolution, with terminal which honour size hints (round height and width to match a full number of columns and rows), and so, sometimes there is gap between windows.
I hope that you can understand my new file : lib/awful/layout/suit/corner.lua.in, and that you will be able to change it to meet the best as it can you need.

Kind regards,

Le lun. 25 mai 2015 à 10:20, Alexis BRENON <brenon.alexis <at> gmail.com> a écrit :

Hi Rena,

I don't use spiral or dwindle layout, so I don't exactly know how they behave. Nevertheless, I think that they are the nearest to what you try to achieve.

I never implement a new layout, so I can't really help you for the moment. I suggest you to copy one of spiral or dwindle and try to modify it. I will try this also. I will tell you if I manage anything.

Kind regards,

Le ven. 22 mai 2015 à 23:40, Rena <hyperhacker <at> gmail.com> a écrit :
On Fri, May 22, 2015 at 3:16 AM, Alexis BRENON <brenon.alexis <at> gmail.com> wrote:
> Hi Rena,
> It seems quite similar to spiral or zig-zag layouts, doesn't ? Dis you try
> them ? Maybe you can create a new layout based on these which better fits
> your needs.
> Kind regards,
> Alexis
> Le ven. 22 mai 2015 à 02:49, Rena <hyperhacker <at> gmail.com> a écrit :
>> How can I achieve a layout like this? http://i.imgur.com/lNF0fpw.png
>> --
>> Sent from my Game Boy.
>> --
>> To unsubscribe, send mail to awesome-unsubscribe <at> naquadah.org.

Those layouts appear to divide the screen area repeatedly in half?
It's not quite what I'm after. Perhaps if I could adjust them a bit.
The spiral, dwindle, and fair layouts don't seem to let me resize any
windows and ignore the nmaster/ncols settings; not sure if that's a

I think my first image wasn't clear, maybe an animation will help:

Basically with most layouts there's one row or column for "master"
windows and N for "non-master" windows (where N is adjustable). What
I'm looking for is the non-master windows to be in both rows *and*
columns, with the master window(s) in a corner.

I might have a go at implementing it myself, but I'm not really sure
where to begin there.

Sent from my Game Boy.
Attachment (corner_layout.patch): text/x-patch, 6459 bytes
Carlo Cabanilla | 24 May 05:20 2015

Moving a window's audio when moving monitors

Hello Awesome people,

I have a setup at home where I have my desktop connected to a monitor and speakers, and also connected to my tv which has its own speakers. I'd like to have it so that when I move a window playing sound like a youtube tab or mplayer from my monitor to my tv, the sound also switches from my desktop speakers to my monitor speakers. Is there an easy way to do this?

My idea was to create a timer that would call `pacmd list-sink-inputs` to get the current things that are playing sound and build a table that maps pid to sink input id (the thing playing sound) and sink id (the set of speakers it's currently playing sound out of) and every few seconds checks all the awesome clients to make sure that their sink id matched the screen that they were on. If they didn't make, called `pacmd move-sink-input` to move their sink id to the appropriate on.

The problem I'm running into is that I'm using the pid to match pulseaudio sink inputs with awesome clients, but for Chrome tabs for example, different clients will have the same pid but will be on different screens. Is there a better id I could match on? I was considering using the X window id, but I didn't know how to get that value from pulseaudio's sink inputs.