Re: Fixing Firefox focus stealing

[Abraham Baker]

That setting also helps if you're using an external RSS feed reader (e.g. 
newsbeuter) to help avoid switching focus back to FF when opening links.


Abe


From: Jan Larres 
Sent: Tuesday, September 27, 2016 11:55:44 PM
To: awesome@naquadah.org
Subject: Re: Fixing Firefox focus stealing


A better option for Firefox specifically is to set the
"browser.tabs.loadDivertedInBackground" option to "true" in about:config,
which stops Firefox from trying to grab the focus when loading a URL remotely.

-Jan


--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.

Mouse wrapping?

[Abraham Baker]

Hi,


When I shift focus between monitors in Awesome, I can "wrap" the focus from the 
right-most monitor back to the left/first one.  So, I could cycle focus between 
all the monitors indefinitely.


How would I make the mouse-controlled cursor do the same thing? For example, if 
I moused over the right border of the right-most monitor, the cursor would then 
jump to the left-most monitor's left border.  Is this outside the scope of the 
window manager?


Thanks,

Abe

Tag switching question

[Abraham Baker]

Hi,


Nothing "broken" here, but just curious about a strange phenomenon:


A very handy shortcut is built in to switch between tags on the same screen 
(Super + Esc).  This works great when I hold Super first and then tap Esc.  
However, when I hold Esc first instead and then tap Super, it flickers between 
the tags for half a second.


Any clues why this is?


Abe

Super + Esc Tag Switching: doesn't work at first

[Abraham Baker]

Hi,


Minor bug I've noticed:


Right when I start awesome, if I try to switch between tags on the same screen 
using Super (Mod4) + Esc, it doesn't work until I manually switch back to the 
first tag once.


For example:

  *   I start on tag 1 of the middle screen
  *   I switch manually to tag 7 of the middle screen (Super + 7)
  *   I try to switch back to tag 1 on the same screen with Super + Esc, but it 
doesn't work
  *   I switch back using Super+1 instead
  *   Now when I use Super+Esc I can toggle between tags 1 and 7 on the same 
screen

Is it possible that I have something set up wrong, or is this default behavior?


Thanks,

Abe

Re: Mod4 no longer responding

[Abraham Baker]

Alexis: I think you're right; I just tested another keyboard with the same
setup, and its Mod4 key worked (strangely its function key did not
work...).

I doubt that the actual key has broken on my keyboard: it's mechanical, and
2 keys on opposite ends of the board breaking at once seems unlikely. So, I
think a recent update might have broken support for my keyboard.

I've been using this to provide support for the extra keys on the side of
my keyboard:
https://github.com/Wattos/logitech-g710-linux-driver

Up until now, this driver has worked well and I have never had any "broken"
keys like this before.  Nobody's made any commits to this for a few years,
so perhaps the driver is no longer compatible with newer linux kernels (I'm
using 4.6.3-1-ARCH).

I'll try the Mod4 key on another operating system later just to make sure
it isn't a physical problem.

Thanks,
Abe

On Wed, Jul 13, 2016 at 5:14 AM, Alexis BRENON 
wrote:

> Same idea. I xev doesn't report Mod4 events, it's probably deeper than an
> awesome config mistake, something related to X11, udev, etc. ?
>
> Le mer. 13 juil. 2016 à 08:04, Namikaze Minato  a
> écrit :
>
>> The only think I can say is that the rc.lua change you described here
>> cannot have caused your mod key to stop working.
>> Did you try to see if your mod4 key works outside of the graphical
>> environment to try to understand what is happening?
>>
>> Regards,
>> LLoyd
>>
>> On 13 July 2016 at 04:39, Abraham Baker 
>> wrote:
>> > Hi,
>> >
>> > My Mod4 (SuperL and R) keys stopped working today after I altered my
>> rc.lua
>> > to make switching client focus easier.
>> >
>> > All I did was to switch the default binding of "Mod4 + Control + j/k" to
>> > "Mod4 + Control + h/l" for changing the screen.focus_relative.  Using H
>> and
>> > L to move the focus left and right makes more intuitive sense to me
>> because
>> > my monitors are arranged linearly.
>> >
>> > I remembered to change the tag.incncol bindings as well, since they were
>> > already using Mod4 + Control + h/l.
>> >
>> > However, after making these changes, I now cannot use Mod4 at all (it
>> does
>> > not register in xev). If I restore the config to the way it was before,
>> Mod4
>> > still does not work. Switching to Alt (Mod1) works, but I would much
>> rather
>> > use Mod4 if possible.
>> >
>> > Any help in figuring out how to restore Mod4 functionality would be
>> greatly
>> > appreciated.
>> >
>> > Thanks,
>> > Aber
>>
>> --
>> To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
>>
>

Mod4 no longer responding

[Abraham Baker]

Hi,

My Mod4 (SuperL and R) keys stopped working today after I altered my rc.lua
to make switching client focus easier.

All I did was to switch the default binding of "Mod4 + Control + j/k" to
"Mod4 + Control + h/l" for changing the screen.focus_relative.  Using H and
L to move the focus left and right makes more intuitive sense to me because
my monitors are arranged linearly.

I remembered to change the tag.incncol bindings as well, since they were
already using Mod4 + Control + h/l.

However, after making these changes, I now cannot use Mod4 at all (it does
not register in xev). If I restore the config to the way it was before,
Mod4 still does not work. Switching to Alt (Mod1) works, but I would much
rather use Mod4 if possible.

Any help in figuring out how to restore Mod4 functionality would be greatly
appreciated.

Thanks,
Aber

Re: FullScreens function problem

[Abraham Baker]

All I had to do to fix it was change my 20-nvidia.conf (similar to
xorg.conf) using nvidia-settings to set the left-most monitor as my
"primary" display.

Now shift + Mod + f makes the client, no matter which screen it is on,
stretch across all three monitors as intended.

Thanks for clearing up the part about screen numbering!
Abe

On Sun, Jun 12, 2016 at 3:19 PM, Uli Schlachter  wrote:

> Hi,
>
> Am 12.06.2016 um 19:59 schrieb Abraham Baker:
> [...]
> > However, I need the client's upper-left corner to start on screen 0, but
> > when I change the index to 0, I get an error: "invalid screen number: 0".
>
> Lua counts things starting from 1. So 1 is the first screen, 2 the second
> etc.
> There is no screen 0.
>
> > xrandr claims that there is one screen (screen #0) with 3 displays
> > attached.  Do I need to set nvidia-settings to have 3 separate screens,
> or
> > can this function work the way it is currently set up?
>
> ...and screens in awesome's don't have anything to do with screens in
> xrandr's
> output. They have something to do with outputs as listed in RandR.
>
> So... what exactly is the problem that you are trying to solve by changing
> some
> 1 into a 0? And where did you do that? Do you perhabs want a 2 (or 3)
> instead of
> 0 here?
>
> Cheers,
> Uli
>
> --
> "Are you preparing for another war, Plutarch?" I ask.
> "Oh, not now. Now we're in that sweet period where everyone agrees that our
> recent horrors should never be repeated," he says. "But collective
> thinking is
> usually short-lived. We're fickle, stupid beings with poor memories and a
> great
> gift for self-destruction.
>

FullScreens function problem

[Abraham Baker]

Hi,

I recently added another monitor to my desktop, so I wanted to try out the
FullScreens function as found here:
https://awesomewm.org/wiki/FullScreens

However, I need the client's upper-left corner to start on screen 0, but
when I change the index to 0, I get an error: "invalid screen number: 0".

xrandr claims that there is one screen (screen #0) with 3 displays
attached.  Do I need to set nvidia-settings to have 3 separate screens, or
can this function work the way it is currently set up?

Thanks,
Abe

Re: AwesomeWM + Gvim resize crashes (segfault)

[Abraham Baker]

Also not helpful:  have you tried just using vim in xterm?  That works
great for me, but you might be using plugins/features that terminal vim
doesn't support.  But, if you are just using vanilla Gvim, then you might
consider giving terminal vim a try.

Abe

On Sat, Apr 30, 2016 at 11:16 AM, Uli Schlachter  wrote:

> Hi,
>
> Am 30.04.2016 um 16:28 schrieb Jeroen Budts:
> [...]
> > When starting gvim with `strace gvim -V9log.txt file.tex > stdout.txt 2>
> > stderr.txt` I got the following in stdout.txt:
> > RenderBadPicture (invalid Picture parameter)
> > Vim: Got X error
> > Vim: Finished.
> >
> > Any help on this is much appreciated.
>
> I know that this isn't helpful at all, but this sounds like a problem with
> GVim.
> A BadPicture means that gvim sent a request to the X11 server to act on
> some
> picture, but that picture does not exist (or is not suitable for this
> request
> due to some other reason). The window manager has nothing to do with
> Pictures,
> so hm.
>
> The only recommendations that I can give is to try other (newer?) versions
> of
> gvim, gtk and cairo (the drawing library used by gtk).
>
> Sorry & good luck,
> Uli
> --
> 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 awesome-unsubscr...@naquadah.org.
>

Re: Naughty Notifications on multiple monitors

[Abraham Baker]

Once again, updating to awesome v3.5.9 led to me needing to re-edit line
600 of naughty.lua.

Is there a way I can permanently implement this change, or should I just
anticipate this for every update?

Thanks,
Abe

On Wed, Feb 3, 2016 at 8:02 PM, Abraham Baker 
wrote:

> Just in case anyone finds this interesting/useful:
> After updating to awesome v3.5.8, I had to re-remove the .id from line 600
> of naughty.lua to avoid the error I got before.
>
> Re-removing the .id returned the notification behavior to the way it was,
> which works really well!
>
> Abe
>
> On Fri, Jun 5, 2015 at 11:58 AM, Abraham Baker 
> wrote:
>
>> Hi,
>>
>> Changing naughty.lua:600 to
>> local id = naughty.notify(args) --no .id
>> results in notifications on all screens + no error! Thanks!
>>
>> So, for clarification, my naughy.lua now looks like this on line 600:
>> local id = naughty.notify(args)
>>
>> and my rc.lua looks like this where the local naughty module is defined:
>> local naughty = require("naughty")
>> naughty.notify_ = naughty.notify
>> naughty.notify = function (args,...)
>>for i = 1, screen.count() do
>>args.screen = i
>>naughty.notify_(args,...)
>>end
>> end
>>
>> @David: removing the .id part in naughty.lua:600 is necessary to prevent
>> the error that happens when not trying to deal with keeping the id's in a
>> table (which is what Alexis was suggesting). If I understand it correctly,
>> if you want to be able to change the same notification without creating a
>> new one, you have to manage the id's.
>>
>> e.g. without managing id's, changing the backlight from 0 to 100% might
>> result in 100 1% notifications piling up!
>>
>> However, since I don't use high-frequency notifications on my desktop, I
>> can ignore the need for notification id's for now.
>>
>> Thanks everyone!
>> Abe
>>
>> On Fri, Jun 5, 2015 at 8:31 AM, David Sorkovsky <
>> davidsorkov...@hotmail.com> wrote:
>>
>>>
>>>
>>> Of I understand the…
>>>
>>>
>>>
>>> local naughty = require("naughty")
>>> naughty.notify_ = naughty.notify
>>> naughty.notify = function (args,...)
>>>for i = 1, screen.count() do
>>>args.screen = i
>>>naughty.notify_(args,...)
>>>end
>>> end
>>>
>>>
>>>
>>>
>>>
>>> … code correctly, would you even need to modify naughty.lua?
>>>
>>>
>>>
>>>
>>>
>>> Regards
>>>
>>>
>>>
>>> Dave
>>>
>>>
>>> --
>>>
>>> *From:* Alexis BRENON [mailto:brenon.ale...@gmail.com]
>>> *Sent:* Friday, 5 June 2015 11:07 PM
>>> *To:* Abraham Baker
>>> *Cc:* Elv1313 .; awesome
>>> *Subject:* Re: Naughty Notifications on multiple monitors
>>>
>>>
>>>
>>> Instead of hidding the error just replace line 600 from:
>>> local id = naughty.notify(args).id
>>>
>>> to
>>>
>>> naughty.notify(args)
>>>
>>>
>>>
>>> You don't need the id any more if you don't use it. This way, no more
>>> error.
>>>
>>> Le ven. 5 juin 2015 à 14:57, Abraham Baker 
>>> a écrit :
>>>
>>> Hi,
>>>
>>> My goal is to get every notification to show up on all monitors.  This
>>> isn't critical; it just makes switching between standing/sitting easier.
>>>
>>>
>>> I don't use often-updating notifications, so I (for now) don't care
>>> about the notification id's.  So, I'm thinking Elv1313's solution + hiding
>>> the naughty.lua:600 error would be enough.
>>>
>>>
>>>
>>> The relevant part of my rc.lua:
>>>
>>> -- Standard awesome library
>>> local gears = require("gears")
>>> local awful = require("awful")
>>> awful.rules = require("awful.rules")
>>> require("awful.autofocus")
>>> -- Widget and layout library
>>> local wibox = require("wibox")
>>> -- Theme handling library
>>> local beautiful = require("beautiful")
>>> -- Notification library
>>>
>>>
>>> local naughty = require("naughty")
>>> naughty.notify_ = naughty.notify
>>> naughty.notify = functio

Awesome Wikipedia UBX

[Abraham Baker]

Hi,

I've made a Wikipedia userbox for the Awesome WM:
https://en.wikipedia.org/wiki/Wikipedia_talk:Userboxes/New_Userboxes#March_11.2C_2016
https://en.wikipedia.org/wiki/User:Myoglobin/Userboxes/Awesome_WM

I just wanted to mention it here before adding it to the Software UBX
page.  I'm not sure whether it should go under "Desktop Environments",
"Other Software", or if I should suggest a new section for "Window Manager"
(there are some wms under the Other section already, but they could be
moved).

https://en.wikipedia.org/wiki/Wikipedia:Userboxes/Software#Other

Hope this is useful to some of you!

Abe

Re: Redshift, no effect?

[Abraham Baker]

I just start redshift-gtk on boot, and the icon shows up in the bar at the
top.  Seems to just work, but I guess this wouldn't help if you can't use
gtk for some reason.

Abe

On Sun, Feb 28, 2016 at 10:18 AM, A M  wrote:

> Hello
>
> I've setup redshift integration as described in these two links:
> https://awesome.naquadah.org/wiki/Using_redshift_with_awesome
> https://github.com/YoRyan/awesome-redshift/blob/master/README.md
>
> I've followed the instructions carefully and imitated them precisely. As
> far as I am aware of all dependencies are fulfilled (redshift and xrandr is
> installed) .
> I am getting no results at all. I've added the key-binding for
> redshift.toggle and nothing happens when triggering it.
>
> I'm using Fedora 23 with awesome 3.5.8 (Major Tom)
>
> Should these instructions work with recent versions of awesome (they
> appear to be a few years old)?
> Is anyone else successfully using redshift?
> How can I debug and determine the issue?
>
> Best Regards
> Alex
>
> --
> To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
>

Re: Key bindings for shutdown, reboot?

[Abraham Baker]

I just map Shift+Pause/break to "systemctl suspend" or "reboot" or
"poweroff":
awful.key({"Shift"}, "#127", function () awful.util.spawn("systemctl
suspend") end),

I haven't needed a dialog yet since it would be really hard to press both
Shift and Pause at the same time by accident, but that looks like a great
idea for when other people need to shutdown the computer.

On Sun, Feb 21, 2016 at 5:57 AM, Daniel Sont  wrote:

> Really, all you need is zenity. If you look into the docs I imagine it
> should be easy to hook up a confirmation box to a shutdown command with
> some &&s
> On Feb 21, 2016 8:53 PM, "Daniel Sont"  wrote:
>
>> I just ran into this: http://awesome.naquadah.org/wiki/ShutdownDialog
>> On Feb 21, 2016 8:48 PM, "A M"  wrote:
>>
>>> Hello
>>>
>>> Is possible to create key bindings for shutting down or rebooting the
>>> computer?
>>>
>>> As a next step, it might be good to have some form of secondary
>>> confirmation that the user really wants to do this action (in case the key
>>> binding was entered accidentally). I guess maybe some simple popup
>>> window/dialog might be an easy solution? "Reboot computer? Yes/No"
>>>
>>> Best Regards
>>> Alex
>>>
>>> --
>>> To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
>>>
>>

Re: Naughty Notifications on multiple monitors

[Abraham Baker]

Just in case anyone finds this interesting/useful:
After updating to awesome v3.5.8, I had to re-remove the .id from line 600
of naughty.lua to avoid the error I got before.

Re-removing the .id returned the notification behavior to the way it was,
which works really well!

Abe

On Fri, Jun 5, 2015 at 11:58 AM, Abraham Baker 
wrote:

> Hi,
>
> Changing naughty.lua:600 to
> local id = naughty.notify(args) --no .id
> results in notifications on all screens + no error! Thanks!
>
> So, for clarification, my naughy.lua now looks like this on line 600:
> local id = naughty.notify(args)
>
> and my rc.lua looks like this where the local naughty module is defined:
> local naughty = require("naughty")
> naughty.notify_ = naughty.notify
> naughty.notify = function (args,...)
>for i = 1, screen.count() do
>args.screen = i
>naughty.notify_(args,...)
>end
> end
>
> @David: removing the .id part in naughty.lua:600 is necessary to prevent
> the error that happens when not trying to deal with keeping the id's in a
> table (which is what Alexis was suggesting). If I understand it correctly,
> if you want to be able to change the same notification without creating a
> new one, you have to manage the id's.
>
> e.g. without managing id's, changing the backlight from 0 to 100% might
> result in 100 1% notifications piling up!
>
> However, since I don't use high-frequency notifications on my desktop, I
> can ignore the need for notification id's for now.
>
> Thanks everyone!
> Abe
>
> On Fri, Jun 5, 2015 at 8:31 AM, David Sorkovsky <
> davidsorkov...@hotmail.com> wrote:
>
>>
>>
>> Of I understand the…
>>
>>
>>
>> local naughty = require("naughty")
>> naughty.notify_ = naughty.notify
>> naughty.notify = function (args,...)
>>for i = 1, screen.count() do
>>args.screen = i
>>naughty.notify_(args,...)
>>end
>> end
>>
>>
>>
>>
>>
>> … code correctly, would you even need to modify naughty.lua?
>>
>>
>>
>>
>>
>> Regards
>>
>>
>>
>> Dave
>>
>>
>> --
>>
>> *From:* Alexis BRENON [mailto:brenon.ale...@gmail.com]
>> *Sent:* Friday, 5 June 2015 11:07 PM
>> *To:* Abraham Baker
>> *Cc:* Elv1313 .; awesome
>> *Subject:* Re: Naughty Notifications on multiple monitors
>>
>>
>>
>> Instead of hidding the error just replace line 600 from:
>> local id = naughty.notify(args).id
>>
>> to
>>
>> naughty.notify(args)
>>
>>
>>
>> You don't need the id any more if you don't use it. This way, no more
>> error.
>>
>> Le ven. 5 juin 2015 à 14:57, Abraham Baker  a
>> écrit :
>>
>> Hi,
>>
>> My goal is to get every notification to show up on all monitors.  This
>> isn't critical; it just makes switching between standing/sitting easier.
>>
>>
>> I don't use often-updating notifications, so I (for now) don't care about
>> the notification id's.  So, I'm thinking Elv1313's solution + hiding the
>> naughty.lua:600 error would be enough.
>>
>>
>>
>> The relevant part of my rc.lua:
>>
>> -- Standard awesome library
>> local gears = require("gears")
>> local awful = require("awful")
>> awful.rules = require("awful.rules")
>> require("awful.autofocus")
>> -- Widget and layout library
>> local wibox = require("wibox")
>> -- Theme handling library
>> local beautiful = require("beautiful")
>> -- Notification library
>>
>>
>> local naughty = require("naughty")
>> naughty.notify_ = naughty.notify
>> naughty.notify = function (args,...)
>>for i = 1, screen.count() do
>>args.screen = i
>>naughty.notify_(args,...)
>>end
>> end
>>
>> local menubar = require("menubar")
>> local revelation=require("revelation")
>> -- {{{ Error handling
>> -- Check if awesome encountered an error during startup and fell back to
>> -- another config (This code will only ever execute for the fallback
>> config)
>> if awesome.startup_errors then
>> naughty.notify({ preset = naughty.config.presets.critical,
>>  title = "Oops, there were errors during startup!",
>>  text = awesome.startup_errors })
>> end
>>
>> -- Handle runtime errors after start

Re: Making conky un-minimizable

[Abraham Baker]

This is not directly relevant, but have you heard of/tried the "Revelation"
extension (https://github.com/guotsuan/awesome-revelation)?

It helps you find specific windows when you have a lot of stuff open.

Abe

On Wed, Dec 23, 2015 at 2:08 AM, Greg Bell  wrote:

> I have Conky set up much like here:
> http://awesome.naquadah.org/wiki/Conky_HUD
>
> However, when I get window-clutter-overwhelm, I like to hold down Mod4 + n
> and just minimize everybody and start over again.
>
> Problem is, when I get to the desktop, often Conky is up so it gets
> minimized too.  Once that happens the toggle (conky.ontop) doesn't work any
> more.  I have to killall -9 conky, then re-run it.
>
> It has "focusable = false" in the properties, like in the wiki, so I would
> have thought this couldn't happen.
>
> What am I doing wrong?
>
>
> Many thanks,
> Greg
>
> --
> To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
>

Re: Reparenting windows manager

[Abraham Baker]

If I use imagej on linux, I have to add "run_once('export
_JAVA_AWT_WM_NONREPARENTING=1')" to the awesome rc.lua, and even then menus
don't work.

run_once is a function suggested on the awesome wiki to work like
awful.util.spawn_with_shell(), except it doesn't run programs already
running if you restart awesome.

On Thu, Oct 8, 2015 at 9:13 AM, Javier Jaramago Fernandez <
jaramago.fernandez.jav...@gmail.com> wrote:

> Hello good afternoon,
>
> does anybody know if awesome is already a re-parenting windows manager?
> I'm asking because it still have Java issues even when the problems were
> supposed to be caused because awesome was a non-re-parenting windows
> manager. If anybody knows we could trace the problem and try to fix it in
> the OpenJdk at least (if they are the bug source).
>
> Thanks you.
>
> --
> Javier Jaramago Fernández.
>

Re: tag switcher does not accept clicks after resolution change with xrandr

[Abraham Baker]

I forgot to mention that once this bug kicks in, I can't delete
notifications by clicking them as I used to be able to (e.g. next song in
playlist pops up, I can't dismiss the notification and have to wait for it
to go away).  This didn't happen after I changed my config to show
notifications on both screens, so I don't think this bug is related to that.

On Wed, Sep 23, 2015 at 6:31 AM, Abraham Baker 
wrote:

> Hi,
>
> I also have this problem, but it seems to happen after a certain amount of
> time has passed after boot (about an hour), and I don't need to change my
> monitor rotation to cause this.  I do sometimes use xrandr, since one of my
> monitors can rotate, so I use an xrandr command to rotate it, but this bug
> happens even when I don't do that after booting.
>
> Perhaps my problem is related to the feh-based wallpaper changer I use.
> In the past, something similar happened because I used conky and it set
> itself to be covering some of the tag number by default...
>
> I don't really use the actual tag buttons very much, but it's frustrating
> when I try to and it doesn't work. It will be interesting to see what the
> real cause of this problem is!
>
> Thanks,
> Abe
>
> On Wed, Sep 23, 2015 at 3:02 AM, Razvan Rotari 
> wrote:
>
>> Hi,
>>
>> I have the same problem after using the using the "Cycling through
>> possible configurations" from
>> http://awesome.naquadah.org/wiki/Using_Multiple_Screens.
>> In my case the window list will not respond to click too.
>>
>> Regards,
>> Razvan
>>
>>
>> On 2015-09-23 10:53, Manner Róbert wrote:
>>
>>> Hi,
>>>
>>> I have a quite annoying problem: once I change the resolution with
>>> xrandr, the desktop switcher buttons stop working. I can not click on them,
>>> I can only switch between them with the keyboard.
>>> Same happens with the layout switcher button on the top right.
>>>
>>> Did anyone observe the same problem? Do you have an idea what can cause
>>> this?
>>>
>>> ---
>>>
>>> I do not use any custom switcher widget, but the one which comes with
>>> awesome. I am using the current awesome version in archlinux.
>>>
>>> $ awesome --version
>>> awesome v3.5.6 (For Those About To Rock)
>>>  • Build: May  5 2015 05:45:29 for x86_64 by gcc version 5.1.0
>>> (builduser@)
>>>  • Compiled against Lua 5.3.0 (running with Lua 5.3)
>>>  • D-Bus support: ✔
>>>
>>> I have intel card.
>>>
>>> Thanks for any help in advance,
>>>
>>> Robert
>>>
>>
>>
>> --
>> To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
>>
>
>

Re: tag switcher does not accept clicks after resolution change with xrandr

[Abraham Baker]

Hi,

I also have this problem, but it seems to happen after a certain amount of
time has passed after boot (about an hour), and I don't need to change my
monitor rotation to cause this.  I do sometimes use xrandr, since one of my
monitors can rotate, so I use an xrandr command to rotate it, but this bug
happens even when I don't do that after booting.

Perhaps my problem is related to the feh-based wallpaper changer I use.  In
the past, something similar happened because I used conky and it set itself
to be covering some of the tag number by default...

I don't really use the actual tag buttons very much, but it's frustrating
when I try to and it doesn't work. It will be interesting to see what the
real cause of this problem is!

Thanks,
Abe

On Wed, Sep 23, 2015 at 3:02 AM, Razvan Rotari  wrote:

> Hi,
>
> I have the same problem after using the using the "Cycling through
> possible configurations" from
> http://awesome.naquadah.org/wiki/Using_Multiple_Screens.
> In my case the window list will not respond to click too.
>
> Regards,
> Razvan
>
>
> On 2015-09-23 10:53, Manner Róbert wrote:
>
>> Hi,
>>
>> I have a quite annoying problem: once I change the resolution with
>> xrandr, the desktop switcher buttons stop working. I can not click on them,
>> I can only switch between them with the keyboard.
>> Same happens with the layout switcher button on the top right.
>>
>> Did anyone observe the same problem? Do you have an idea what can cause
>> this?
>>
>> ---
>>
>> I do not use any custom switcher widget, but the one which comes with
>> awesome. I am using the current awesome version in archlinux.
>>
>> $ awesome --version
>> awesome v3.5.6 (For Those About To Rock)
>>  • Build: May  5 2015 05:45:29 for x86_64 by gcc version 5.1.0 (builduser@
>> )
>>  • Compiled against Lua 5.3.0 (running with Lua 5.3)
>>  • D-Bus support: ✔
>>
>> I have intel card.
>>
>> Thanks for any help in advance,
>>
>> Robert
>>
>
>
> --
> To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
>

Re: advice

[Abraham Baker]

Alex mentioned compositors, which reminded me of a question I should have
asked ages ago:

The last time I tried enabling compositing (to get transparent terminals so
I can see my wallpapers), I found that using compton led to the terminal
text not refreshing fast enough (e.g. while scrolling in ranger or
newsbeuter), so I had to disable it.  I notice that I can enable
transparency in the awesome wm interface itself without problems (using
rgba), so I'm not sure exactly what went wrong. Is there currently a
solution to this, or has anyone else even had this problem?


On Tue, Sep 8, 2015 at 1:22 PM, Bruno Ferreira  wrote:

> @ray I like the configurations that get installed with Manjaro Awesome
> respin (https://github.com/Culinax/manjaro-awesome-respin). The initial
> configuration may be too minimal. I don't know if you need to install
> packages besides awesome to use this config. use the virtual machine first.
>
> @alexander try searching for "awesome wm" instead of just "awesome"
>
> Cumprimentos,
> Bruno Ferreira
>
> 2015-09-08 19:14 GMT+01:00 Alexander Tsepkov :
>
>> Not sure what you want to hear. If you've expecting to hear a sales pitch
>> on awesome, I don't think there is a need, you're installing a free wm, not
>> buying a car, just test it in virtualbox first if you're worried. If you're
>> asking about specific features of a modern wm, they're all there - some not
>> through vm itself (for example I installed awesome on top of xfce and use
>> thunar file manager, and several xfce widgets). It's been a while since I
>> installed awesome, I didn't like the idea of tiling wms at first, but now
>> got so used to it I installed hammerspoon on my OSX to emulate it.
>>
>> Awesome works fine out of the box, I don't remember if I had to do
>> anything to get my dual-monitors working but xrandr drives that and I
>> mapped windows+P to switch between display setups via bash script. One
>> thing to note is that keyboard shortcuts weren't intuitive to me right away
>> so I switched some around. The default theme is also pretty ugly, but
>> replacing it with one of preset ones from github is pretty easy (
>> https://github.com/copycat-killer/awesome-copycats). It also doesn't
>> come with a compositor at first (so no shadows or transparent windows you
>> may be used to), but that's a good thing since it gives you more
>> flexibility. I use compton as my compositor and really like it. Unless you
>> plan to customize your look and feel, you don't really need much lua. There
>> are available widgets like volume, networking, etc. you can plug in (and
>> will need to do if your theme doesn't already come with them). My only pet
>> peeve with awesome is it's name, try googling for anything regarding
>> awesome and see how often the first page contains a relevant result.
>>
>> On Tue, Sep 8, 2015 at 1:58 PM, Ray Andrews 
>> wrote:
>>
>>> Gentlemen,
>>>
>>> I use xfce, it's fine, but I want something lighter.  All I really want
>>> is the xfwm part of it, and even that window manager has its defects. I
>>> have dual monitors, and I can't drag anything between monitors.  I hate
>>> trying to configure things using those stupid pop up dialogue boxes.
>>> I'd like text configuration files that I can edit, save, backup and
>>> restore.
>>>
>>> Awesome seems well spoken of.  What can you guys tell me?  I can't
>>> think what to specifically ask.  It would be nice if it worked sensibly
>>> out of the box.  I don't need fancy effects.  I want windows on screens
>>> that I can resize, maximize, minimize, etc.  Nice if they snap to
>>> borders to avoid wasted space.  Xfce gives normally six or so desktops
>>> than you can change to, that's good.  The mouse has to work.  I need
>>> custom keyboard shortcuts.  Basically nothing strange.  I don't want to
>>> have to spend six months learning Lua.  I want a simple, predictable,
>>> configurable WM that is usable but doesn't bother me with bells and
>>> whistles.
>>>
>>> Advice?
>>>
>>
>>
>

Random error?

[Abraham Baker]

Hi,

I just got this random error that occured without any kind of trigger:
Oops, an error happened!
/usr/share/lua/5.3/lgi/component.lua:302: bad arg #2 to 'element'
(Pango.Layout expected, got userdata)

This happened many hours after I booted up; I haven't restarted awesome by
itself today for any reason, and I haven't changed any config settings
today.

I'm using Arch but I haven't updated very recently; I'll update and see if
that prevents this from happening again.

The only thing that I can think of that might have caused this error is
that I've suspended/resuspended a lot today, which sometimes causes
problems like the taskwarrior server quitting and failing to restart.

This error itself doesn't seemed to have broken anything.

In the future, would it be better to send info about bugs like this to
https://github.com/awesomeWM/awesome/issues , or is this mailing list just
as good?

Thank you,
Abe

Dual-Monitor Systray

[Abraham Baker]

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

Re: Naughty Notifications on multiple monitors

[Abraham Baker]

Hi,

Changing naughty.lua:600 to
local id = naughty.notify(args) --no .id
results in notifications on all screens + no error! Thanks!

So, for clarification, my naughy.lua now looks like this on line 600:
local id = naughty.notify(args)

and my rc.lua looks like this where the local naughty module is defined:
local naughty = require("naughty")
naughty.notify_ = naughty.notify
naughty.notify = function (args,...)
   for i = 1, screen.count() do
   args.screen = i
   naughty.notify_(args,...)
   end
end

@David: removing the .id part in naughty.lua:600 is necessary to prevent
the error that happens when not trying to deal with keeping the id's in a
table (which is what Alexis was suggesting). If I understand it correctly,
if you want to be able to change the same notification without creating a
new one, you have to manage the id's.

e.g. without managing id's, changing the backlight from 0 to 100% might
result in 100 1% notifications piling up!

However, since I don't use high-frequency notifications on my desktop, I
can ignore the need for notification id's for now.

Thanks everyone!
Abe

On Fri, Jun 5, 2015 at 8:31 AM, David Sorkovsky 
wrote:

>
>
> Of I understand the…
>
>
>
> local naughty = require("naughty")
> naughty.notify_ = naughty.notify
> naughty.notify = function (args,...)
>for i = 1, screen.count() do
>args.screen = i
>naughty.notify_(args,...)
>end
> end
>
>
>
>
>
> … code correctly, would you even need to modify naughty.lua?
>
>
>
>
>
> Regards
>
>
>
> Dave
>
>
>  --
>
> *From:* Alexis BRENON [mailto:brenon.ale...@gmail.com]
> *Sent:* Friday, 5 June 2015 11:07 PM
> *To:* Abraham Baker
> *Cc:* Elv1313 .; awesome
> *Subject:* Re: Naughty Notifications on multiple monitors
>
>
>
> Instead of hidding the error just replace line 600 from:
> local id = naughty.notify(args).id
>
> to
>
> naughty.notify(args)
>
>
>
> You don't need the id any more if you don't use it. This way, no more
> error.
>
> Le ven. 5 juin 2015 à 14:57, Abraham Baker  a
> écrit :
>
>Hi,
>
> My goal is to get every notification to show up on all monitors.  This
> isn't critical; it just makes switching between standing/sitting easier.
>
>
> I don't use often-updating notifications, so I (for now) don't care about
> the notification id's.  So, I'm thinking Elv1313's solution + hiding the
> naughty.lua:600 error would be enough.
>
>
>
> The relevant part of my rc.lua:
>
> -- Standard awesome library
> local gears = require("gears")
> local awful = require("awful")
> awful.rules = require("awful.rules")
> require("awful.autofocus")
> -- Widget and layout library
> local wibox = require("wibox")
> -- Theme handling library
> local beautiful = require("beautiful")
> -- Notification library
>
>
> local naughty = require("naughty")
> naughty.notify_ = naughty.notify
> naughty.notify = function (args,...)
>for i = 1, screen.count() do
>args.screen = i
>naughty.notify_(args,...)
>end
> end
>
> local menubar = require("menubar")
> local revelation=require("revelation")
> -- {{{ Error handling
> -- Check if awesome encountered an error during startup and fell back to
> -- another config (This code will only ever execute for the fallback
> config)
> if awesome.startup_errors then
> naughty.notify({ preset = naughty.config.presets.critical,
>  title = "Oops, there were errors during startup!",
>  text = awesome.startup_errors })
> end
>
> -- Handle runtime errors after startup
> do
> local in_error = false
> awesome.connect_signal("debug::error", function (err)
> -- Make sure we don't go into an endless error loop
> if in_error then return end
> in_error = true
>
> naughty.notify({ preset = naughty.config.presets.critical,
>  title = "Oops, an error happened!",
>  text = err })
> in_error = false
> end)
> end
> -- }}}
>
>  The relevant part of naughty.lua (the only part changed from default):
> local id = naughty.notify(args).id
> return "u", id
> --local notifs = naughty.notify(args)
> --local id = {}
> --for notif in ipairs(notifs) do
> --  id:insert(notif.id)
> --end
>
> Thanks,
>
> Abe
>
>
>
> On Fri, Jun 5, 2015 at 2:22 AM, Alexis BRENON 
> wrote:
>
> Hi Abraham,
>
&

Re: Naughty Notifications on multiple monitors

[Abraham Baker]

Hi,

My goal is to get every notification to show up on all monitors.  This
isn't critical; it just makes switching between standing/sitting easier.

I don't use often-updating notifications, so I (for now) don't care about
the notification id's.  So, I'm thinking Elv1313's solution + hiding the
naughty.lua:600 error would be enough.

The relevant part of my rc.lua:

-- Standard awesome library
local gears = require("gears")
local awful = require("awful")
awful.rules = require("awful.rules")
require("awful.autofocus")
-- Widget and layout library
local wibox = require("wibox")
-- Theme handling library
local beautiful = require("beautiful")
-- Notification library
local naughty = require("naughty")
naughty.notify_ = naughty.notify
naughty.notify = function (args,...)
   for i = 1, screen.count() do
   args.screen = i
   naughty.notify_(args,...)
   end
end
local menubar = require("menubar")
local revelation=require("revelation")
-- {{{ Error handling
-- Check if awesome encountered an error during startup and fell back to
-- another config (This code will only ever execute for the fallback config)
if awesome.startup_errors then
naughty.notify({ preset = naughty.config.presets.critical,
 title = "Oops, there were errors during startup!",
 text = awesome.startup_errors })
end

-- Handle runtime errors after startup
do
local in_error = false
awesome.connect_signal("debug::error", function (err)
-- Make sure we don't go into an endless error loop
if in_error then return end
in_error = true

naughty.notify({ preset = naughty.config.presets.critical,
 title = "Oops, an error happened!",
 text = err })
in_error = false
end)
end
-- }}}


The relevant part of naughty.lua (the only part changed from default):
local id = naughty.notify(args).id
return "u", id
--local notifs = naughty.notify(args)
--local id = {}
--for notif in ipairs(notifs) do
--  id:insert(notif.id)
--end

Thanks,
Abe

On Fri, Jun 5, 2015 at 2:22 AM, Alexis BRENON 
wrote:

> Hi Abraham,
>
> I'm sorry, I don't understand what and when did commented out ?
> Can you please post your config file on pastebin (http://pastebin.com/)
> or something like that (github?).
>
> To fix the error about 'insert' method, you can replace the line :
> notifications:insert(i, naughty.notify_(args,...))
> by
> table.insert(notifications, i, naughty.notify)
>
> Maybe you will have also to cheat a little bit if i doesn't start to 1...
>
> Maybe I can explain you a little deeper what are the goals, this way you
> will be able to debug yourself.
>
> So, you want to have your notifications displayed on many screens (the
> exact number is not important).
> To do so, you have to redefine the classic naughty.notify function, to
> call the initial naughty.notify function with the screen arg which loop
> over all your screen. This is what is done by the code sent by Elv1313.
>
> Nevertheless, the initial notify function returns a table representing the
> notification, containing for example an ID (the id field). If you don't
> need it, so fine, stick to the Elv1313 solution and remove any
> naughty.notify(...).id code in your config.
> But this ID can be useful if you need to replace a notification instead of
> adding a new one (this can be the case if you use notification to display
> volume changement, backlight modification, battery alert, whatever).
> To handle this, your new notify function must return the created
> notifications, or at least their ID.
> This is what my code intend to do. For each call to the initial notify
> function, I put the resulting table in a 'result' table, indexed by the
> index of the screen on which the notification is displayed. Up to ypu after
> to use it the right way.
>
> The last chunk of code I sent you, handle the case where you want to use
> the replaces_id argument of notify. As, in your case, you will have not
> only one, but many notifications to replace (one on each screen), you will
> pass the replaces_id argument as a table. This is not handled by the
> initial notify function, so for the actual call you use the value at the
> index representing your screen, as we do for the 'screen' arg.
>
> I hope the reasonning is clear.
>
> Alexis
>
> Le ven. 5 juin 2015 à 05:13, Abraham Baker  a
> écrit :
>
>> Hi,
>>
>> When I commented out 600 and 601 of naughty.lua *before* changing
>> rc.lua, I got:
>> naughty.lua:604: bad arg #1 to 'ipairs' (table expected, got nil)
>> 

Re: Naughty Notifications on multiple monitors

[Abraham Baker]

Hi,

When I commented out 600 and 601 of naughty.lua *before* changing rc.lua, I
got:
naughty.lua:604: bad arg #1 to 'ipairs' (table expected, got nil)
on both screens.

Then, when I added the updated naughy.notify function to rc.lua, I got:
rc.lua:22 attempt to call a nil value (method 'insert')
on only one screen

Ironically, the previous solution would work perfectly if it wasn't for the
error messages (which are critical and have to be clicked away)!
Is there a way to selectively silence the error messages related to
naughty.lua without silencing all errors?

Thanks,
Abe


On Thu, Jun 4, 2015 at 2:08 AM, Alexis BRENON 
wrote:

> Hum, well, you will have to update a little bit your config!
>
> First, the default naughty.notify function returns a table representing
> the notification, but your new notify function doesn't, so update it :
>
> naughty.notify_ = naughty.notify
> naughty.notify = function (args,...)
>   notifications = {}
>for i = 1, screen.count() do
>args.screen = i
>notifications:insert(i, naughty.notify_(args,...))
>end
>return notifications
> end
>
> Then line 600 you update to something like :
> local notifs = naughty.notify(args)
> local id = {}
> for notif in ipairs(notifs) do
>   id:insert(notif.id)
> end
>
> Nevertheless, I think that you use the id value to replace the
> notification, do you ? In this case, you will have to update again your
> custom notification to handle the case if args.id is a table (instead of
> a number) :
>
> naughty.notify = function (args,...)
>notifications = {}
>naughty_args = args
>for i = 1, screen.count() do
>if args.replaces_id and type(args.replaces_id) == "table" then
>   naughty_args.replaces_id = args.replaces_id[i]
>end
>naughty_args.screen = i
>notifications:insert(i, naughty.notify_(args,...))
>end
>return notifications
> end
>
> Or something like that.
>
> Cheers,
> Alexis
>
> Le mer. 3 juin 2015 à 22:30, Abraham Baker  a
> écrit :
>
>> That actually works, but also generates an error (in the form of a
>> critical notification on both screens) at the same time:
>> /usr/share/awesome/lib/naughty.lua:600: attempt to index a nil value
>>
>> For context, line 600 is:
>> local id = naughty.notify(args).id
>>
>> Looks like this is close to working right! Thanks!
>>
>> On Wed, Jun 3, 2015 at 2:24 PM, Elv1313 .  wrote:
>>
>>> This should help:
>>>
>>> local naughty = require('naughty')
>>> naughty.notify_ = naughty.notify
>>> naughty.notify = function (args,...)
>>>for i = 1, screen.count() do
>>>args.screen = i
>>>naughty.notify_(args,...)
>>>end
>>> end
>>>
>>> On 3 June 2015 at 10:42, Abraham Baker 
>>> wrote:
>>> > I tried adding that code right after the local naughty =
>>> require("naughty")
>>> > that was already there, but it didn't work and actually stopped any
>>> > notifications from showing on any monitor.
>>> >
>>> > I doubt it was the cause, but some other functions in my rc.lua also
>>> use
>>> > local i as a counter;  these shouldn't interfere with each other as
>>> long as
>>> > they are inside their own functions, right?
>>> >
>>> > Thanks,
>>> > Abe
>>> >
>>> > On Wed, Jun 3, 2015 at 8:20 AM, Alexis BRENON >> >
>>> > wrote:
>>> >>
>>> >> Hi Abraham,
>>> >>
>>> >> you have to call the anughty.notift() function twice, once for each
>>> >> screen.
>>> >> Maybe you can define a function which do it for you :
>>> >>
>>> >> local naughty = require('naughty')
>>> >> naughty.notify = function (args)
>>> >> local i = 1
>>> >> while i <= screen.count() do
>>> >> args.screen = i
>>> >> naughty.notify(args)
>>> >> end
>>> >> end
>>> >>
>>> >> Or something like that
>>> >>
>>> >> Regards,
>>> >> Alexis
>>> >>
>>> >> Le mer. 3 juin 2015 à 15:13, Abraham Baker 
>>> a
>>> >> écrit :
>>> >>>
>>> >>> Hi,
>>> >>>
>>> >>> 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?
>>> >>>
>>> >>> Thanks,
>>> >>> Abe Baker
>>> >
>>> >
>>>
>>
>>

Re: Naughty Notifications on multiple monitors

[Abraham Baker]

That actually works, but also generates an error (in the form of a critical
notification on both screens) at the same time:
/usr/share/awesome/lib/naughty.lua:600: attempt to index a nil value

For context, line 600 is:
local id = naughty.notify(args).id

Looks like this is close to working right! Thanks!

On Wed, Jun 3, 2015 at 2:24 PM, Elv1313 .  wrote:

> This should help:
>
> local naughty = require('naughty')
> naughty.notify_ = naughty.notify
> naughty.notify = function (args,...)
>for i = 1, screen.count() do
>args.screen = i
>naughty.notify_(args,...)
>end
> end
>
> On 3 June 2015 at 10:42, Abraham Baker  wrote:
> > I tried adding that code right after the local naughty =
> require("naughty")
> > that was already there, but it didn't work and actually stopped any
> > notifications from showing on any monitor.
> >
> > I doubt it was the cause, but some other functions in my rc.lua also use
> > local i as a counter;  these shouldn't interfere with each other as long
> as
> > they are inside their own functions, right?
> >
> > Thanks,
> > Abe
> >
> > On Wed, Jun 3, 2015 at 8:20 AM, Alexis BRENON 
> > wrote:
> >>
> >> Hi Abraham,
> >>
> >> you have to call the anughty.notift() function twice, once for each
> >> screen.
> >> Maybe you can define a function which do it for you :
> >>
> >> local naughty = require('naughty')
> >> naughty.notify = function (args)
> >> local i = 1
> >> while i <= screen.count() do
> >> args.screen = i
> >> naughty.notify(args)
> >> end
> >> end
> >>
> >> Or something like that
> >>
> >> Regards,
> >> Alexis
> >>
> >> Le mer. 3 juin 2015 à 15:13, Abraham Baker 
> a
> >> écrit :
> >>>
> >>> Hi,
> >>>
> >>> 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?
> >>>
> >>> Thanks,
> >>> Abe Baker
> >
> >
>

Re: Naughty Notifications on multiple monitors

[Abraham Baker]

I tried adding that code right after the local naughty = require("naughty")
that was already there, but it didn't work and actually stopped any
notifications from showing on any monitor.

I doubt it was the cause, but some other functions in my rc.lua also use
local i as a counter;  these shouldn't interfere with each other as long as
they are inside their own functions, right?

Thanks,
Abe

On Wed, Jun 3, 2015 at 8:20 AM, Alexis BRENON 
wrote:

> Hi Abraham,
>
> you have to call the anughty.notift() function twice, once for each screen.
> Maybe you can define a function which do it for you :
>
> local naughty = require('naughty')
> naughty.notify = function (args)
> local i = 1
> while i <= screen.count() do
> args.screen = i
> naughty.notify(args)
> end
> end
>
> Or something like that
>
> Regards,
> Alexis
>
> Le mer. 3 juin 2015 à 15:13, Abraham Baker  a
> écrit :
>
>> Hi,
>>
>> 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?
>>
>> Thanks,
>> Abe Baker
>>
>

Naughty Notifications on multiple monitors

[Abraham Baker]

Hi,

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?

Thanks,
Abe Baker

Re: advices for widget

[Abraham Baker]

For automatically mounting usb drives with an icon in the tray to control
mounting/unmounting, installing udiskie and then running udiskie --tray
works well.

https://github.com/coldfix/udiskie
https://awesome.naquadah.org/wiki/Automounting#Udiskie

On Wed, Jun 3, 2015 at 3:28 AM, Sławomir Kowalewski <
slawomir.kowalew...@gmail.com> wrote:

> Hi Mickael,
>
> There is also very nice lain widget library and here you can see same
> examples and ready to use configs
> https://github.com/copycat-killer/awesome-copycats
>
> On 3 June 2015 at 08:45, Alexis BRENON  wrote:
>
>> Hi Mickael,
>>
>> For battery state and volume control, I use Vicious library (
>> https://awesome.naquadah.org/wiki/Vicious)
>> I use it also for clock but I implemented calendar manually, based on the
>> work of Vincent Bernat (
>> https://github.com/AlexisBRENON/awesome-configuration/blob/master/backend/datetime/calendar.lua
>> ).
>>
>> For wifi and more generally network controller, I never found anything as
>> good as NetworkManager with nm-applet. I tried all in this list
>> https://wiki.archlinux.org/index.php/List_of_applications/Internet#Network_managers
>> .
>>
>> I didn't use any easy drive mounter, as I don't have many external drives
>> or USB key. Only one good rule in /etc/fstab a folder named /mnt/external,
>> and I only have to type "mount /etc/external" to mount my USB drive when
>> needed.
>>
>> Hope my experience can help.
>>
>> Kind regards,
>> Alexis
>>
>> Le mar. 2 juin 2015 à 17:05, mickael foucaux 
>> a écrit :
>>
>>> 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.
>>>
>>> cheers,
>>>
>>> Mickael
>>>
>>
>