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 brenon.ale...@gmail.com
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 z1693...@students.niu.edu 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 . elv1...@gmail.com 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 z1693...@students.niu.edu
 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 brenon.ale...@gmail.com
 
  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 z1693...@students.niu.edu
 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]

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 brenon.ale...@gmail.com
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 z1693...@students.niu.edu 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)
 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

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

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

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?
>>>
>>
>>
>

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: 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 <z1693...@students.niu.edu>
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 <am3rikn...@gmail.com>
> 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: 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: 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 <z1693...@students.niu.edu>
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 <z1693...@students.niu.edu> 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 st

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.
>

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: 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 <z1693...@students.niu.edu>
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 <z1693...@students.niu.edu>
> 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 <z1693...@students.niu.edu>
>>> 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

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.
>

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

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

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