Re: New Lua object system

At 1239502049 time_t, koniu wrote: Maybe here's one - screen:tags(arg) fails to set the tag table properly for #arg 1. Only the first tag in arg table makes it into the screen. Good catch, should be fixed now. Cheers, -- Julien Danjou // ᐰ jul...@danjou.info http://julien.danjou.info //

[PATCH] titlebar.lua: more buttons added

This is a new version of 'titlebar.lua'. There are now additional buttons for: - setting the 'ontop' attribute - setting the 'sticky' attribute - maximizing the client In addition to changing the state of the client the buttons also show if the corresponding state is active for a client. All new

Re: New Lua object system

Good catch, should be fixed now. Works like a charm, death to FS493 :] thanks o/ koniu -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.

Re: [PATCH] titlebar.lua: more buttons added

At 1239537269 time_t, Thomas Brunko wrote: Wah, that's a very nice patch! Congrats. A couple of things: * Do not put --- in front of your comments or local function, or the documentation would be added in luadoc. Since it's a local function, we don't want to add doc in user doc. So just --

[awesome bugs] #493 - setting tag.screen wipes tags properties

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#493 - setting tag.screen wipes tags properties User who did this - Julien Danjou (jd) Reason for closing: Fixed Additional comments about closing: Fixed with new object system. More information can be found at

Re: [PATCH] titlebar.lua: more buttons added

At Sun, 12 Apr 2009 15:11:06 +0200 Julien Danjou wrote: At 1239537269 time_t, Thomas Brunko wrote: Wah, that's a very nice patch! Congrats. A couple of things: * Do not put --- in front of your comments or local function, or the documentation would be added in luadoc. Since it's a

keyboard not working?

Hi ppl, I git pulled recently and now nothing works anymore. Specifically it seams awesome works flawlessly but ignores the keyboard completely, and since awesome is keyboard based its a pain to use. I am working with the default rc.lua and erased /usr/share/awesome and reinstalled but the

Re: keyboard not working?

At 1239564802 time_t, Alex Cornejo wrote: I git pulled recently and now nothing works anymore. Specifically it seams awesome works flawlessly but ignores the keyboard completely, and since awesome is keyboard based its a pain to use. I am working with the default rc.lua and erased

Re: keyboard not working?

Yes, I believe so. The latest commit in my xcb-util is 88fdd1bc23c608f712f20bd9f65cad22c6fb711b (commited by you today). Do I need to be following some other branch? I've been pulling xcb-util from git://anongit.freedesktop.org/git/xcb/util Cheers, Alex On Sun, Apr 12, 2009 at 3:51 PM,

Re: keyboard not working?

Hi, On 12 Apr - 16:07, Alex Cornejo wrote: Yes, I believe so. The latest commit in my xcb-util is 88fdd1bc23c608f712f20bd9f65cad22c6fb711b (commited by you today). Do I need to be following some other branch? I've been pulling xcb-util from git://anongit.freedesktop.org/git/xcb/util Had

Re: keyboard not working?

Also, if you haven't, try my regular oh wtf it brokes! special: rm -Rf /usr/local/share/awesome rm -Rf /awesome/source/dir/.build-something-goes-here make sudo make install. Fixes a lot of problems that have to do with files appearing/vanishing, which tends to create some of the most confusing

[PATCH] awful.widget.taglist: dont show name if icon_only property is set

Hi, Here's a trivial patch which allows users to have a tag displayed with an icon only if they set 'icon_only' property for it. Choice of the name might not be the best one, but taglist_icon_only seems terribly long for what it is. awful.tag.setproperty(t, icon_only) koniu From