Re: doc and or examples for obvious
On 26.10.2011 00:11, Thorsten Sperber wrote: Am 25.10.2011 23:12, schrieb Daniel Martí: You might have more luck emailing julien about this. And, if you do get an answer, it would be very kind of you to forward it to this list :-) Oh, the authors of the more interesting (and sadly not working widgets, grepped for Author): /usr/share/awesome/lib/obvious/net/init.lua:-- Author: Uli Schlachter -- /usr/share/awesome/lib/obvious/cpu/init.lua:-- Author: Uli Schlachter -- /usr/share/awesome/lib/obvious/io/init.lua:-- Author: Uli Schlachter -- /usr/share/awesome/lib/obvious/mem/init.lua:-- Author: Uli Schlachter -- And Uli is pretty active here and already responded in this thread :) Oh, and regarding xephyr: yes, I'm using that. On the host desktop I keep said logs scrolling in an xterm so I can see whats going wrong and eventually fix it. Hm, ok, let's get creative: $ lua -e 'f=io.open(/proc/stat) l=f:read() for k in l:gmatch(%d+) do print(k) end' That's what the cpu widget does to gets its data. The rest is some maths on the result. Does that work for you? Uli -- - He made himself, me nothing, you nothing out of the dust - Er machte sich mir nichts, dir nichts aus dem Staub -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: Maximise window moving
On Wed, Oct 26 2011, Perry Hargrave wrote: Is this the same as fs#917? https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=917 Looks so. We should release 3.4.11 now I guess. -- Julien Danjou pgpbaDBStoOB3.pgp Description: PGP signature
Re: Maximise window moving
On 26.10.2011 10:10, Julien Danjou wrote: On Wed, Oct 26 2011, Perry Hargrave wrote: Is this the same as fs#917? https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=917 Looks so. We should release 3.4.11 now I guess. Before that, I'd like someone to actually test the stuff I recently committed to 3.4, please. Well, not committed, more like cherry-picked-and-hoped-it-works. Uli -- - He made himself, me nothing, you nothing out of the dust - Er machte sich mir nichts, dir nichts aus dem Staub -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: doc and or examples for obvious
On 26.10.2011 09:29, Uli Schlachter wrote: Hm, ok, let's get creative: $ lua -e 'f=io.open(/proc/stat) l=f:read() for k in l:gmatch(%d+) do print(k) end' That's what the cpu widget does to gets its data. The rest is some maths on the result. Does that work for you? Uli Yes, works so far (spits out some cpu values). I also found out that the non-working widgets use obvious.lib.widget, so it might just be a usage error on my side. myStatus[s].widgets = [...] obvious.cpu(), -- doesnt work wisep, -- seperator obvious.loadavg(), -- works wisep, obvious.mem(), -- doesnt work wisep, obvious.net.recv(eth0), -- doesnt work obvious.net.send(eth0), -- neither wisep, obvious.basic_mpd(), -- a little buggy on my arch box, works on debian - have to look for myself wisep, obvious.volume_alsa(), -- works, great widget wisep, obvious.fs_usage(), -- doesnt work [...] Did I miss something? There's no readme or such, so I used those like the others... Thorsten -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: doc and or examples for obvious
On 26.10.2011 12:46, Thorsten Sperber wrote: On 26.10.2011 09:29, Uli Schlachter wrote: Hm, ok, let's get creative: $ lua -e 'f=io.open(/proc/stat) l=f:read() for k in l:gmatch(%d+) do print(k) end' That's what the cpu widget does to gets its data. The rest is some maths on the result. Does that work for you? Uli Yes, works so far (spits out some cpu values). I also found out that the non-working widgets use obvious.lib.widget, so it might just be a usage error on my side. myStatus[s].widgets = [...] obvious.cpu(), -- doesnt work wisep, -- seperator obvious.loadavg(), -- works wisep, obvious.mem(), -- doesnt work wisep, obvious.net.recv(eth0), -- doesnt work obvious.net.send(eth0), -- neither wisep, obvious.basic_mpd(), -- a little buggy on my arch box, works on debian - have to look for myself wisep, obvious.volume_alsa(), -- works, great widget wisep, obvious.fs_usage(), -- doesnt work [...] Let's try something inspired by Rainux Luo's config: obvious.mem() obvious.mem().widget, obvious.mem()[1], obvious.mem()[1].widget, Perhaps one of those works? Uli -- - Buck, when, exactly, did you lose your mind? - Three months ago. I woke up one morning married to a pineapple. An ugly pineapple... But I loved her. -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Direction of moving windows between screens (monitors)
Hello, after adding third monitor to my setup I've encountered a small problem. Up to this time, when I wanted to send application window to another monitor I used 'Mod4+o', which ofc calls awful.client.movetoscreen function. Now the things are more complicated, because sometimes I want to send window to left monitor, sometimes to the right one. Is there a simple way to achieve this, or do I need to modify the movetoscreen function in awful? I see it has the 's' parameter, but from what I see it allows only to pass the screen numberm not the 'direction' itself. thanks for help, Paweł Rumian -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: doc and or examples for obvious
On 26.10.2011 13:53, Uli Schlachter wrote: Let's try something inspired by Rainux Luo's config: obvious.mem() obvious.mem().widget, obvious.mem()[1], obvious.mem()[1].widget, Perhaps one of those works? Uli The second one works for mem, cpu, fs_usage and net. These are the ones I tested. I think, I might have overseen the solution some days ago (I already tested .widget), because I tested with cpu and since the obvious widgets don't have a background (and my CPU usage is mostly under 5%), I misunderstood the empty space for an error. So some widgets need .widget, some not...it's a small bug in the obvious lib, I guess. Thorsten -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: Maximise window moving
On 26.10.2011 19:49, Adrian C. wrote: On Wed, 26 Oct 2011, Uli Schlachter wrote: Before that, I'd like someone to actually test the stuff I recently committed to 3.4, please. Well, not committed, more like cherry-picked-and-hoped-it-works. Arch Linux users are prevented because of: c9f6b65c: Update the code following release of xcb-util 0.3.8. That won't help them if we release awesome 3.4.11 with that commit. Meh, what good did arch ever do? :-( Uli -- Do you know that books smell like nutmeg or some spice from a foreign land? -- Faber in Fahrenheit 451 -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
[awesome bugs] #936 - Moving a maximized window fails
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#936 - Moving a maximized window fails User who did this - Uli Schlachter (psychon) Reason for closing: Duplicate Additional comments about closing: Duplicate of FS#917 More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=936 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
[awesome bugs] #936 - Moving a maximized window fails
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#936 - Moving a maximized window fails User who did this - Javier Barroso (i5513) -- I recompile with that changes, but the same behaviour :( (I had to change liblua5.1-dev to liblua5.1-0-dev in build depends) I can't compile awesome 3 with http://awesome.naquadah.org/wiki/Awesome-3-git-debian instructions, seems like dependencies are not longer valid ? Thanks for your efforts! -- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=936#comment2768 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
