Re: Tag Switching Mildly Broken in 3.4.12
On Thu, Jun 14, 2012 at 05:29:07PM +0200, Marco wrote:
On 2012-06-13 Leo L. Schwab ew...@ewhac.org wrote:
This new behavior doesn't appear to be mentioned in the changelog.
Is this an intended change? Is there a way to work around it in rc.lua?
Do you have any sticky programs running that paint on the root
window? It might be that they steal the focus. Is that the case,
then you can stop them from doing so with a rule. Here is my rule
for nautilus:
In my case, the program is an old-ish system monitor program called
'gkrellm', and is currently configured with the sticky bit set. Following
your suggestion, I added the following to my awful.rules.rules:
{ rule = { class = Gkrellm, sticky = true },
properties = { focus = false } },
After restarting Awesome, everything is fine, window focus behaves
as before, and I thought I was done.
However, if I click inside the gkrellm window to (for example)
change the music track or change the volume, then gkrellm starts snarfing
the focus away again, and switching tags leaves no windows selected. So the
problem persists.
Is there anything else I could fiddle with?
BTW, as a consequence of diving in to Awesome to better understand
how rules work, I ended up writing a Wiki page that hopefully describes what
I learned:
https://awesome.naquadah.org/wiki/Understanding_Rules
Schwab
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: New lgi dependency and older Ubuntu LTS
2012/6/17 Uli Schlachter psyc...@znc.in: Short version: You need /usr/lib/girepository-1.0/Pango-1.0.typelib (in debian this is in package gir1.2-pango-1.0). Uli, you are absolutely great. Now I not only have my awesome working again, but I understand the whole 'introspection' thing :) Thank you! For future reference: in Gentoo you need to have x11-libs/pango built with USE='introspection' BR, Paweł -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
os.setlocale stopped working in git?
Hello, after recent update of awesome I had troubles starting it with my config file (it worked fine with the default one). Some investigation lead me to the first line of my rc.lua: os.setlocale(os.getenv(LANG)) With this line, awesome crashes at start with: /usr/share/awesome/lib/gears/surface.lua:12: attempt to compare nil with number /etc/xdg/awesome/rc.lua:2: loop or previous error loading module 'awful' E: awesome: main:555: couldn't find any rc file When I comment the os.setlocale line, everything is OK. Why is this happening? Is there another way to get the textclock display date in my native language? BR, Paweł -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: os.setlocale stopped working in git?
OK, it works when I call os.setlocale after local awful = require(awful) I guess it is one of the recent changes in awful that causes this. Still a very minor problem, as awful does not need to use my locale and I can call setlocale after loading awful. Paweł -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
shifty - tab creation rules - creating one tag on each screen automatically
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi I have some applications, for which I would like to have a tag of the same name on each screen (I have two screens). Is this possible? At the moment, when I start the program, it creates one tag on one screen, and I manually create one on the other screen, but it would be really nice if this could be done automatically? Thanks, Rainer -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/fELwACgkQoYgNqgF2egqZegCfebdC5KsBAj7NhmstMxGPMKfI HeEAoIKekzaloF3JCvLHdRraAJV5B/SS =0xKb -END PGP SIGNATURE- -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Moving tag from one screen to the other
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi is it possible to move tags from one screen to the other? Either via keyboard shortcut (like Modkey-o for clients) or via mouse? Thanks, Rainer -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/fE74ACgkQoYgNqgF2egrU3ACfdlyRfmX3nEswqRJyOh71O2p0 sfcAn2W7KnX0Q/UBAgCPLesfZWGGqQox =hcQW -END PGP SIGNATURE- -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: New lgi dependency and older Ubuntu LTS
On 6/17/2012 6:19 PM, Uli Schlachter wrote: On 17.06.2012 18:06, Giorgos Keramidas wrote: On Sun, Jun 17, 2012 at 2:48 PM, Uli Schlachter psyc...@znc.in wrote: On 17.06.2012 12:31, Giorgos Keramidas wrote: [...] Some of the dependencies of the lgi code cannot be met at all on my aging Ubuntu installation. [...] /etc/lsb-release says: Ubuntu 10.04.1 LTS Hm. Wikipedia says Ubuntu 10.04 is supported until 2013-04. That's still quite a while. Sounds like we shouldn't release 3.5 before then. ;-) Awesome already used Pango before and Pango used gobject before. The only new dependency (besides lgi) should be on gobject-introspection. Version 0.10.8 was releases in May 2011. That's a little more recent than I had thought. However, I have no good idea what could be done about this. I don't know what's new in gobject-introspection 0.10.8 and thus can't say why older versions don't work. Sounds like someone (I?) should write a mail to lgi upstream and ask for details... No need to, upstream is here and listening :-) Ubuntu Lucid supports only 0.6 series of gobject-introspection. Thats pretty bad, because so many bugfixes, many useful API additionas and even a few API/ABI changes were done since then. Current lgi code basically depends on gobject-introspection=1.30, with hacks added here and there to support goi=0.10 version. I was hoping to nuke those hacks in the next release, but it looks that I'll have to keep them. As for supporting 0.6.x series; almost definitely impossible with current lgi sourcebase. I'm having my small personal summer of code project, rewriting a lot of lgi internals, and (for unrelated reasons) it should lessen the dependency on exact version of gobject-introspection, so that 0.6.x could be usable (with some additional effort). But don't hold your breath, it might take a few months before I get it into the releasable shape. As Uli said above, installing newer gobject-introspection into the $HOME will probably not work, I'm afraid that .typelib files (coming from other packages) will not be compatible with it. The only solution would be to build locally (into your $HOME) the Gnome stack parts up to pango (which would also include gobject-introspection). Gnome's jhbuild[0] makes this quite a painless experience (at least for me it was). sorry for not so good news, Pavel [0] http://developer.gnome.org/jhbuild/unstable -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: New lgi dependency and older Ubuntu LTS
On Mon, Jun 18, 2012 at 3:25 PM, Pavel Holejsovsky pavel.holejsov...@gmail.com wrote: As Uli said above, installing newer gobject-introspection into the $HOME will probably not work, I'm afraid that .typelib files (coming from other packages) will not be compatible with it. The only solution would be to build locally (into your $HOME) the Gnome stack parts up to pango (which would also include gobject-introspection). Gnome's jhbuild[0] makes this quite a painless experience (at least for me it was). I can't build so many parts of the Gnome stack on this machine, for various reasons (security team constraints among them). So I'll have to wait until Precise Pangolin rolls out to my work desktop I guess. Thanks for all the useful information though. Much appreciated! Cheers, Giorgos
Re: shifty - tab creation rules - creating one tag on each screen automatically
On Jun 18, 2012 4:28 AM, Rainer M Krug r.m.k...@gmail.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
I have some applications, for which I would like to have a tag of the
same name on each screen (I
have two screens). Is this possible? At the moment, when I start the
program, it creates one tag
on one screen, and I manually create one on the other screen, but it
would be really nice if this
could be done automatically?
Are you asking if shifty can create tags on startup?
shifty.config.tag = {
foo = { screen = 1, init = true },
}
You can also see an example here:
https://github.com/bioe007/awesome-shifty/blob/master/example.rc.lua
Re: shifty - tab creation rules - creating one tag on each screen automatically
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18/06/12 18:34, Perry Hargrave wrote:
On Jun 18, 2012 4:28 AM, Rainer M Krug r.m.k...@gmail.com
mailto:r.m.k...@gmail.com
wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
Hi
I have some applications, for which I would like to have a tag of the same
name on each
screen (I have two screens). Is this possible? At the moment, when I start
the program, it
creates one tag on one screen, and I manually create one on the other
screen, but it would be
really nice if this could be done automatically?
Are you asking if shifty can create tags on startup?
No - the tag is created by an application matching rule, where I specify screen
= 1 ; but I would
like to create automatically two tags: one on screen 1 and 1 on screen two when
I launch that
application.
Cheers,
Rainer
shifty.config.tag = {
foo = { screen = 1, init = true },
}
You can also see an example here:
https://github.com/bioe007/awesome-shifty/blob/master/example.rc.lua
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk/fcOYACgkQoYgNqgF2egriTACfU6huCWkF/dydy/RoynTfzj+X
VY8An3WRkOt3KCquqQlvz84ErWjaqgN4
=iS/y
-END PGP SIGNATURE-
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: Another setup question
On 17.06.2012 23:34, Evan Driscoll wrote: On 06/16/2012 01:55 AM, Uli Schlachter wrote: Also, could you install xtrace[0] and run awesome under it? I assume that the last thing in your .xsession is something like exec awesome. Turn that into exec xtrace --relative-timestamps --outfile /tmp/xtrace_output awesome. This tool dumps all of awesome's X11 requests and all replies from the server into a text file. Expect lots of output, so please don't do too much stuff in awesome (e.g. use ctrl+c, a key binding or ctrl-alt-backspace instead of the menu to close it). I'd be interested in the resulting xtrace_output file. OK, it's attached. Thanks for the help, by the way. Uhm. Could you triple check if this really is cairo 1.12? This cannot happen. :-/ The picture 0x00200010 is used but was never created at all. Picture 0x002f is used five requests after it was created. Also, there is weird scaling factor (0.842102) applied to that picture before it is freed. This cannot even be explained with another cairo version. I have just no clue what is going on. :-( Perhaps run awesome under valgrind and hope that it reports some random corruption? But that couldn't explain this either... 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.
Viewing Multiple Tags
For some odd reason, my 2nd tag can't be viewed with any other tag using the keyboard hotkey Mod + Control + #. Right clicking the tag works fine. Viewing other tags from the 2nd tag works fine however. I did not touch the default config for those hotkeys. I'm using awesome-git. What could cause this odd behavior? -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: Another setup question
On 06/18/2012 01:45 PM, Uli Schlachter wrote: Uhm. Could you triple check if this really is cairo 1.12? This cannot happen. :-/ I checked 'ldd' of 'awesome', and then checked '/proc/awesome/map' when it was actually running to confirm that the only libcairo loaded is the one I built, which came from cairo-1.12.2.tar.xz. The so filename is libcairo.so.2.11200.2. However, I did do something I'm generally not very good about, which is running 'make check'. Cairo's 'make check' produces a lot of failures and crashes. So I'll probably move the discussion there after I get a bit more information (I'm also getting a funky failure in a glib test). I'll report back here after it's fixed, the tests are fixed but Awesome still fails, or I give up. :-) Evan -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: Viewing Multiple Tags
On Mon, 18 Jun 2012, Hong Shick Pak wrote: What could cause this odd behavior? What's the keycode of 2? It's expected to be 11 to properly bind. -- Adrian C. (anrxc) | anrxc..sysphere.org | PGP ID: D20A0618 PGP FP: 02A5 628A D8EE 2A93 996E 929F D5CB 31B7 D20A 0618 -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
create a function to show up a tooltip or naughty notify of all defined key binds ?
Sometimes I will forget what key binds I defined in my rc.lua.
So I come up with an idea.
Creating a function to show up a tooltip or naughty notify of all defined key
binds.
I think this is a good idea, Awesome should have it. Manpage of default key
binds is not enough
So do you have any method to implement this ?
--
[ stardiviner ] {I hate all of you ! Leave me alone}
IRC(freenode): stardiviner \\ Twitter: @numbchild \\
GnuPG Key fingerprint
9BAA 92BC CDDD B9EF 3B36 CB99 B8C4 B8E5 47C3 2433
signature.asc
Description: Digital signature
Re: create a function to show up a tooltip or naughty notify of all defined key binds ?
Sometimes I will forget what key binds I defined in my rc.lua.
Why do you forget the bindkeys? Because they're wrong :) Choose
another keybindings :)
Creating a function to show up a tooltip or naughty notify of all defined key
binds.
I think this is a good idea, Awesome should have it. Manpage of default key
binds is not enough
Just an idea: create own function which creates the keybindings. E.g.
you create a function named my_awful_key (which replaces awful.key):
function my_awful_key(mod,key,press,DESCRIPTION)
local tmp = {
mod = mod,
key = key,
descr = DESCRIPTION
}
table.insert(keybindings,tmp)
return awful.key(mod,key,press)
end
So when you want to create a keybind you'll call my_awful_key instead
of awful.util.key. Your keybindings will stored in `keybindings' so
you can evalutes its content and can display it in a notify.
But what do you do if you forget the keybind of keybinding-help? :)
I hope it can help you.
Zsolt
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
[awesome bugs] #1007 - Switching client with next client broken in git/master.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Paweł Rumian (gorkypl) Attached to Project - awesome Summary - Switching client with next client broken in git/master. Task Type - Bug Report Category - awful Status - Unconfirmed Assigned To - Operating System - All Severity - Medium Priority - Normal Reported Version - git/master Due in Version - Undecided Due Date - Undecided Details - Switching clients (Mod4+Shift+j/k) does not work in current git/master. A popup appears with the following message: /usr/share/awesome/lib/awful/client.lua:378: bad argument #1 to 'next' (table expected, got number) More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1007 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] #1008 - Mouse function (move/resize) persists until mouse cursor is moved.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Matt T (fatcomma) Attached to Project - awesome Summary - Mouse function (move/resize) persists until mouse cursor is moved. Task Type - Bug Report Category - Core Status - Unconfirmed Assigned To - Operating System - Linux Severity - Low Priority - Normal Reported Version - 3.4.11 Due in Version - Undecided Due Date - Undecided Details - To simulate: * MOD+LeftClick on a window to begin a move operation. * Move the mouse cursor. * Result: Window moves as expected. * MOD+RightClick (without first moving cursor) to begin a resize operation. * Move the mouse cursor. * Result: Window is moved instead of resized. The mouse cursor must be moved after an operation before another may be started. Commonly noticed when: Moving a window into a new slot and then immediately attempting to resize it (results in the window moving instead of resizing). More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1008 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] #1008 - Mouse function (move/resize) persists until mouse cursor is moved.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1008 - Mouse function (move/resize) persists until mouse cursor is moved. User who did this - Arvydas Sidorenko (Asido) -- Try to update Awesome. Cannot reproduce -- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1008#comment3052 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] #1006 - Luadoc documentation is broken
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1006 - Luadoc documentation is broken User who did this - Arvydas Sidorenko (Asido) -- What do you think about LDoc? https://github.com/stevedonovan/LDoc It is pretty active project, is comaptible with luadoc rules and more. Although there is a new dependency - Penlight, which is available at luarocks. Otherwise the only option is to extend luadoc with the features we need, right? -- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1006#comment3053 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.
