View next/prev non-empty tag
I would like to have a function for viewing the next and previous non-empty tag (modulo sticky clients I suppose, but I don't really have any of those). I tried to break out and modify the viewnext/viewidx functions from awful.tag, but I messed up. Hacking rc.lua usually goes well, but the capi is a bit tougher. May I ask for some help? Wouldn't be surprised if this is already done somewhere. -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: View next/prev non-empty tag
On 14.02.2012 11:43, Daniel wrote: I would like to have a function for viewing the next and previous non-empty tag (modulo sticky clients I suppose, but I don't really have any of those). I tried to break out and modify the viewnext/viewidx functions from awful.tag, but I messed up. Hacking rc.lua usually goes well, but the capi is a bit tougher. May I ask for some help? Wouldn't be surprised if this is already done somewhere. Dunno if this works, I've written this right now and never tested it: function view_non_empty(step, s) local s = s or 1 -- The following makes sure we don't go into an endless loop -- if no clients are visible. I guess that case could be handled better, -- but meh local num_tags = #screen[s]:tags() for i=1, num_tags do awful.tag.viewidx(step, s) if #awful.tag.visible(s) == 0 then return end end end This won't do what you want when there are sticky clients, but since you usually don't have any sticky clients anyway... Uli -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Too Large Notification Icon?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I had the Problem with some Notifications, but the most anyoing ones come from Banshee (or maybe some other programms too), because Banshee puts the cover of the current title as icon into the notification... i think that gnome handle this with a maxium size for notifications. Is it posible to have a fixed size for notifications too in awesome? Thanks! -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPOnQoAAoJEAhgHfpCPcybiiAH/2Bdz+0kTQV73xJd5RiOTfIf zX3CRwRk40QMfygqGAuG2kUc1mSTpAKNU0n/ly2iEQOWayLfRGQdjWYlbVPEdSdW vVKb/Sg9udnWErah04VWMQfDyH4FPG8h4G8+T4/O8T+fGO/Z7v9QdLJUnlf5EGej tUJSE7weMU9Kd5yWomactqv4O0S0KrRdbRnx9/hvuDPnX4mYwv8WIEvNkQzkGEfT SIeVJja7ev+qtJsflAl9DreSrBT/FzO/MB7b8coYVje+Mc1HoeyOuvJF+anI77Gi dnUAl2nYY/3YfuW2h9yaDqTVpRoAO1h88Z2Sa2jkthwvrDj7quEx+ejMTPpkleA= =UHTX -END PGP SIGNATURE- -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: Too Large Notification Icon?
2012/2/14 Sebastian Bachmann m...@free-minds.net: I had the Problem with some Notifications, but the most anyoing ones come from Banshee (or maybe some other programms too), because Banshee puts the cover of the current title as icon into the notification... I'm not sure if I understand this correctly, but have you tried changing the layout to float while the notification is open? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ cut Is it really needed when posting to a mailing list? greetings, Paweł -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: Too Large Notification Icon?
I think he's talking about tray icons. Isn't he? Maybe the tray icon is enlarging the tray bar and messing with the layout? -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: Too Large Notification Icon?
On 2012-02-14 19:36, Alexander Yakushev wrote: Well, there is a standard convention which declares how the window manager should handle notifications. Awesome uses Naughty for that and there is nothing more on the Awesome side. It could be Banshee's own notifications (Thunderbird used to do that), but then I don't understand how Gnome could anyhow configure their size. Whats really odd is that these look like a naughty notification, but they dont apply to any config i give them... I found some bugs that may apply also to my problem: https://bugzilla.gnome.org/show_bug.cgi?id=649277 Is there any way to get a log of all notifications that naughty put on the screen? -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: Too Large Notification Icon?
Sebastian Bachmann m...@free-minds.net writes: I had the Problem with some Notifications, but the most anyoing ones come from Banshee (or maybe some other programms too), because Banshee puts the cover of the current title as icon into the notification... i think that gnome handle this with a maxium size for notifications. Is it posible to have a fixed size for notifications too in awesome? Thanks! putting this in rc.lua worked for me (with quodlibet notifications, same thing really). naughty.config.default_preset.icon_size = 64 -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: Vicious gmail widget
See attached patch.
Not sure about usefulness of this feature judging just from sample you
provided before. Summary tag suggested it was my e-mail not Joerg's in
your sample, but he was the first one to be listed in an email tag.
--
Adrian C. (anrxc) | anrxc..sysphere.org | PGP ID: D20A0618
PGP FP: 02A5 628A D8EE 2A93 996E 929F D5CB 31B7 D20A 0618--- gmail.lua.bak 2011-03-15 05:05:19.0 +0100
+++ gmail.lua 2012-02-14 20:19:04.0 +0100
@@ -40,7 +40,8 @@
local feed = rss.inbox
local mail = {
[{count}] = 0,
-[{subject}] = N/A
+[{subject}] = N/A,
+[{sender}] = N/A
}
-- }}}
@@ -57,7 +58,6 @@
-- Find subject tags
local title = string.match(line, title(.*)/title)
--- If the subject changed then break out of the loop
if title ~= nil and not string.find(title, feed[2]) then
-- Check if we should scroll, or maybe truncate
if warg then
@@ -70,6 +70,14 @@
-- Spam sanitize the subject and store
mail[{subject}] = helpers.escape(title)
+end
+
+-- Find sender tags
+local from = string.match(line, email(.*)/email)
+-- If the sender changed then break out of the loop
+if from ~= nil then
+-- Spam sanitize the sender and store
+mail[{sender}] = helpers.escape(from)
break
end
end
Re: Too Large Notification Icon?
If it looks like an awesome notification then it is probably the awesome notification. I just thought about another way how Banshee can do this. If it explicitly passes the preferred icon size to be the maximum size of the icon via notify-send (it can do this and the background stuff with hints, I guess). If it is so then the preset values have less priority then the specified ones. On 02/14/2012 08:48 PM, Sebastian Bachmann wrote: Whats really odd is that these look like a naughty notification, but they dont apply to any config i give them... I found some bugs that may apply also to my problem: https://bugzilla.gnome.org/show_bug.cgi?id=649277 Is there any way to get a log of all notifications that naughty put on the screen? -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: Too Large Notification Icon?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 14.02.2012 19:48, Sebastian Bachmann wrote: On 2012-02-14 19:36, Alexander Yakushev wrote: Well, there is a standard convention which declares how the window manager should handle notifications. Awesome uses Naughty for that and there is nothing more on the Awesome side. It could be Banshee's own notifications (Thunderbird used to do that), but then I don't understand how Gnome could anyhow configure their size. Whats really odd is that these look like a naughty notification, but they dont apply to any config i give them... I found some bugs that may apply also to my problem: https://bugzilla.gnome.org/show_bug.cgi?id=649277 Is there any way to get a log of all notifications that naughty put on the screen? Run dbus-monitor in a shell. That will log everything which goes over the session bus, so it might possibly be a lot of output. What we are looking for is stuff that mentions org.freedesktop.Notifications. Uli - -- For saving the Earth.. and eating cheesecake! -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQEcBAEBCAAGBQJPOrqcAAoJECLkKOvLj8sGgwUIANC5BekviIZO6d1yWkAY41WL ZPHbGHBTswq4Ni71sNE4Ww+Vo6cDkIHtswCXxH5MWP9tGVOQx5KGM/cLqdVpWeAS rXkcUpJlsRXAd57up/EpX4CraHzSbA4nCK94ZAQDHlSgVYemNZhII8k1dRuEr3NF vOLu/DuBarPDSxfXaCqdIl//uoL4+GKTedlKs3mGqp07dtMng/Sqi4Wp7OLK7l7B gV6e5kVKwASLFzGv36C9hkZHwZd6slfrOUSCLu1TXc8bQBsrM+ctFffyaXJtxzEw O3pvjIgHa3ucFmYfmdkIzoGwAflrr1oY9Xdyh1Z2SWVqIfGmc72iKDm1lsR4MTQ= =qJ4D -END PGP SIGNATURE- -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Need help submitting menubar
Good evening, I suppose I did everything I could to prepare the Menubar widget for submitting to awesome-git. Now I want to ask in what form I have to send the patch: - Should it be a simple lua independent module or should I send the diff from the current git version with my files inside and .lua.in extensions? - If the second one is correct, where should I put this module? There is more than one file in the module, so it requires its own directory. But it is based on awful's common.list_update and awful.prompt, so it could alternatively become an awful widget. BUT it actually uses modified awful.prompt and I'm not sure it is a good thing to accept modifications to prompt.lua just because of one widget. Best regards, Alexander -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
