Hello,
As maybe every french awesome user, I had to redefine the upper row key
bindings, as the french keymap does not have digits directly on it.
I found a way to use keycodes instead of keysyms to define these
bindings. As keycodes are keymap-independant, this setting should be
convenient to
Hello,
I needed to set a given application's new windows as slaves, the same
way it is done for auto-floating or tagging. For instance, an instant
messenging application's new chat windows can be set as slaves, keeping
the roster window as the master (alone in a small width master column).
So
Hello,
I needed to set a given application's new windows as slaves, the same
way it is done for auto-floating or tagging. For instance, an instant
messenging application's new chat windows can be set as slaves, keeping
the roster window as the master (alone in a small width master column).
So
Hello,
As maybe every french awesome user, I had to redefine the upper row key
bindings, as the french keymap does not have digits directly on it.
I found a way to use keycodes instead of keysyms to define these
bindings. As keycodes are keymap-independant, this setting should be
convenient to
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#581 - honour_size_hints = false sometimes not honoured during manage
User who did this - manshankar (manshankar)
--
I am having same issue. It happens everytime i open a new client. The gaps
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#581 - honour_size_hints = false sometimes not honoured during manage
User who did this - Andrei Thorp (garoth)
--
Using which client, manshankar?
--
More information can be found at the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I just ported obvious (and my rc.lua) to the new timer objects and thought that
the attached patches might be quite usable. It adds a new .started property to
timer objects.
Uli
The following changes since commit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
the attached patch ports obvious to the new timer objects. It depends on the
awesome patch that I just sent. I did some basic testing, but no idea if stuff
like timers.start() and stop() still work. I'll just assume it does. ;)
FYI: The git
At 1250537591 time_t, Uli Schlachter wrote:
Subject: [PATCH 1/2] Add a generic function for read-only properties
Nah, yeah, I'll take care of that anyway. :-)
Subject: [PATCH 2/2] timer: Add a read-only started property
@@ -70,6 +70,13 @@ luaA_timer_get_timeout(lua_State *L, atimer_t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Julien Danjou wrote:
At 1250537591 time_t, Uli Schlachter wrote:
Subject: [PATCH 1/2] Add a generic function for read-only properties
Nah, yeah, I'll take care of that anyway. :-)
Then feel free to rewrite this code / rebase with some of your
At 1250538485 time_t, Uli Schlachter wrote:
Then feel free to rewrite this code / rebase with some of your code.
That's not my plan, actually. I though your observation about getting
information on unknow property access quite interesting to find bad
code. But I don't feel it's the good way to
Excerpts from Uli Schlachter's message of Mon Aug 17 16:07:26 -0400 2009:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Uli Schlachter wrote:
Hi,
the attached patch ports obvious to the new timer objects. It depends on the
awesome patch that I just sent. I did some basic testing,
Thanks, merged (finally) :)
--
GCS/IT/M d- s+:- a-- C++ UL+++ US UB++ P+++ L+++ E--- W+ N+ o--
K- w--- ?O M-- ?V PS++ PE- Y++ PGP+++ t+ 5 X+ R tv b+++ DI+++
D+++ G+ e h! r y+
Gregor Best
pgpdY2uJ1v1eH.pgp
Description: PGP signature
Merged, thanks
--
GCS/IT/M d- s+:- a-- C++ UL+++ US UB++ P+++ L+++ E--- W+ N+ o--
K- w--- ?O M-- ?V PS++ PE- Y++ PGP+++ t+ 5 X+ R tv b+++ DI+++
D+++ G+ e h! r y+
Gregor Best
pgpMoQPOvMSiV.pgp
Description: PGP signature
14 matches
Mail list logo