Re: spawn+tag switch bug
Alex Cornejo [EMAIL PROTECTED] writes: * Example Scenario Suppose you are on tag X, and you want to spawn some heavy application (firefox perhaps), since this will take 2 or 3 seconds, you might switch back to tag Y to continue hacking on something else waiting for the application to load. * Results Since you are at tag Y when the application finishes loading it will up on tag Y instead of tag X (where you actually executed the spawn). * Intended Behaviour It would be nice if awesome somehow rememberd in which tag you where when you executed the spawn command and somehow tagged the application with that tag when it shows up on screen. Suggestions? You can look at http://awesome.naquadah.org/wiki/index.php?title=Original for a starting point, although quick inspection of that code shows that it will get things wrong if you spawn more than one thing at a time. It probably won't deal nicely with things like splashscreens either. -- Espen Wiborg [EMAIL PROTECTED] - Veritas vos liberabit A dime has 118 ridges around the edge. -- To unsubscribe, send mail to [EMAIL PROTECTED]
Re: [PATCH] naughty: introducing urgency levels and presets
At 1227706721 time_t, Leon Winter wrote: I just fixed a minor issue. Please use the url to receive the latest patch ;) Pushed. Cheers, -- Julien Danjou // ᐰ [EMAIL PROTECTED] http://julien.danjou.info // 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD signature.asc Description: Digital signature
Re: spawn+tag switch bug
At 1227712150 time_t, Alex Cornejo wrote: Suggestions? - go to tag 1 - type 'firefox' in a xterm - go to tag 2 - firefox appears on tag 2 Now, can you blame awesome to not seeing you were running firefox? Dude, I know it's an awesome window manager, but it's not an OS. So, impossible to get this workin each time. Maybe if you use ALWAYS menu, prompt, etc it may be doable. But then, you'll have the same problem when, for example, opening a second Firefox window from Firefox. Sorry. Cheers, -- Julien Danjou // ᐰ [EMAIL PROTECTED] http://julien.danjou.info // 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD signature.asc Description: Digital signature
[awesome bugs] #392 - Memory leak caused by Lua code
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#392 - Memory leak caused by Lua code User who did this - Julien Danjou (jd) -- Are you using cairo 1.8.4 ? If you only keep the clock.text part, does it still leak ? -- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=392#comment925 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 [EMAIL PROTECTED]
[awesome bugs] #384 - gkrellm showing up on taskbar if more than 1 gkrellm running
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#384 - gkrellm showing up on taskbar if more than 1 gkrellm running User who did this - Julien Danjou (jd) Reason for closing: Fixed Additional comments about closing: commit 3cc7843f0588ba8a7a0f7927bb9daf65b8802aff Author: Michael Hofmann [EMAIL PROTECTED] Date: Thu Nov 27 11:20:25 2008 +0100 awful.widget: fix iteration over removed elements Signed-off-by: Julien Danjou [EMAIL PROTECTED] More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=384 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 [EMAIL PROTECTED]
[awesome bugs] #392 - Memory leak caused by Lua code
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#392 - Memory leak caused by Lua code User who did this - Julien Danjou (jd) Reason for closing: Not a bug Additional comments about closing: Classic cairo leak, wait for 1.8.5. More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=392 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 [EMAIL PROTECTED]
Re: spawn+tag switch bug
On Thu, Nov 27, 2008 at 10:12:44AM +0100, [EMAIL PROTECTED] wrote: At 1227712150 time_t, Alex Cornejo wrote: Suggestions? - go to tag 1 - type 'firefox' in a xterm - go to tag 2 - firefox appears on tag 2 Yep I noticed something similar with OpenOffice: - go to tag 1 - launch OpenOffice (menu, term or whatever) - while launching (OO splash screen) go to tag 2 OpenOffice appears on tag 2. Now click on OpenOffice menu tag 1 would become visible, tag 2 is now hidden. It's kinda messy. Workaround: be patient until the application had fully started up. tip: it also works for tags different than 1 or 2. -- Sébastien Gross -- To unsubscribe, send mail to [EMAIL PROTECTED]
Re: spawn+tag switch bug
At 1227807090 time_t, Sebastien Gross wrote: Now click on OpenOffice menu tag 1 would become visible, tag 2 is now hidden. It's kinda messy. Don't you refer to some sort of OOo bug? There's a bug under some wm. If you click on a menu it send a change workspace EWMH signal to ask awesome to change the active desktop. -- Julien Danjou // ᐰ [EMAIL PROTECTED] http://julien.danjou.info // 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD signature.asc Description: Digital signature
Re: spawn+tag switch bug
On Thu, Nov 27, 2008 at 17:54, Julien Danjou [EMAIL PROTECTED] wrote: At 1227807090 time_t, Sebastien Gross wrote: Now click on OpenOffice menu tag 1 would become visible, tag 2 is now hidden. It's kinda messy. Look, I really dont want to sound like an ad (again) but if you think that things get messy (which I agree, does happen) and you want to have control over your tags and how clients interact with them, I'd recommend trying shifty extension. Check the wiki page for more explanation: http://awesome.naquadah.org/wiki/index.php?title=Shifty Note that even tho it's a dynamic tagging library and can do quite a few things, you can also quite easily configure it to emulate static tags and just use the client control functionality. koniu ps. (sorry, had to be done :P) -- To unsubscribe, send mail to [EMAIL PROTECTED]
Re: Lua layouts in next
Hey, you probably realize but to even keep track - there's somethings wrong with the lua layouts in next as they are now (unless i managed to misconfigure something badly) but anyway there's some obvious artifacts like missing tiles and such: http://omploader.org/veXc1 Also I've noticed that max layout is now identical to say tile bottom with only one client - there's a gap between the focused (and only visible) client and the bottom/right edges of the workarea, makes my terminal look real bad so I reverted to next before the lua layouts. Someone is looking into this, right? :) o/ koniu -- To unsubscribe, send mail to [EMAIL PROTECTED]
Re: Lua layouts in next
At 1227852775 time_t, koniu wrote: Also I've noticed that max layout is now identical to say tile bottom with only one client - there's a gap between the focused (and only visible) client and the bottom/right edges of the workarea, makes my terminal look real bad so I reverted to next before the lua layouts. That's size hints. Someone is looking into this, right? :) Yes, the port is not complete at all. Gregor send me a patch to fix that. Cheers, -- Julien Danjou // ᐰ [EMAIL PROTECTED] http://julien.danjou.info // 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD signature.asc Description: Digital signature
