On Saturday 09 July 2005 11:44 am, Kim Woelders wrote:
Mike Frysinger wrote:
On Tuesday 05 July 2005 07:56 pm, Tres Melton wrote:
On Tue, 2005-07-05 at 19:05 -0400, Mike Frysinger wrote:
i prefer to use the 'focus follows mouse click' behavior but ive noticed
a quirk in using mouse bindings
On Sunday 10 July 2005 12:19 pm, Mike Frysinger wrote:
just synced up and still experiencing the issue originally described :/
err nm, as kwo pointed out, the checkout tree i was using was out of date
all works now, thanks :)
-mike
---
This
Mike Frysinger wrote:
On Tuesday 05 July 2005 07:56 pm, Tres Melton wrote:
On Tue, 2005-07-05 at 19:05 -0400, Mike Frysinger wrote:
i prefer to use the 'focus follows mouse click' behavior but ive noticed
a quirk in using mouse bindings with it ...
for example, say i have two windows open,
i prefer to use the 'focus follows mouse click' behavior but ive noticed a
quirk in using mouse bindings with it ...
for example, say i have two windows open, Eterm and Gimp ... Eterm currently
has the focus (it gets key strokes, uses the window border has the 'active'
color, and is on top)
On Tue, 2005-07-05 at 19:05 -0400, Mike Frysinger wrote:
i prefer to use the 'focus follows mouse click' behavior but ive noticed a
quirk in using mouse bindings with it ...
for example, say i have two windows open, Eterm and Gimp ... Eterm currently
has the focus (it gets key strokes,
On Tuesday 05 July 2005 07:56 pm, Tres Melton wrote:
On Tue, 2005-07-05 at 19:05 -0400, Mike Frysinger wrote:
i prefer to use the 'focus follows mouse click' behavior but ive noticed
a quirk in using mouse bindings with it ...
for example, say i have two windows open, Eterm and Gimp ...
