On Sun, Jan 20, 2013 at 10:16:15AM +0100, Uli Schlachter wrote:
Hi,
On 20.01.2013 02:08, Nikos Ntarmos wrote:
Still using the 3.4 branch here and I'm bumping on the well-known issue
with clients refusing focus through WM_HINTS and relying on
WM_TAKE_FOCUS instead (e.g., several Wine
Hi there.
I bumped on this problem the other day during an upgrade but didn't have
time to send-pr it. The source of the problem lies here:
On Fri, Feb 04, 2011 at 01:58:28PM -0200, Renato Botelho wrote:
warning: failed to load external entity
Hi there.
FWIW I've also been experiencing segfaults on FreeBSD/i386, however only
when X goes down before awesome. A short look into this revealed it was
due to widgets update hooks being scheduled for some time after
awesome and X is down. I never got around to looking into this any
further but
iterate
through the client tag array till it finds the entry to remove,
otherwise it appends the new entry at the end.
Signed-off-by: Nikos Ntarmos ntar...@cs.uoi.gr
---
lib/awful/client.lua.in | 13 ++---
1 files changed, 10 insertions(+), 3 deletions(-)
diff --git a/lib/awful/client.lua.in
FWIW I've come to believe that Java menus sort-of hardcode their
position in the display (or awesome doesn't inform the app correctly of
its position?). You can click on a menubar item to open a menu but then
what seems like a non-working mouse is due to the fact that the menu
expects the mouse
Just a minor change: since capi.awesome.spawn does a double fork, there
is no need to use a '' to background the spawned process.
Cheers.
\n\n
From 843d7cc255afb8d07e7c91a3a9d1ed706bc07c88 Mon Sep 17 00:00:00 2001
From: Nikos Ntarmos ntar...@cs.uoi.gr
Date: Sun, 29 Mar 2009 21:40:57 +0300
Hey guys.
If there's anyone out there using awesome2, could you please have a look
at the (trivial) patch for #156? It works for me but that's hardly
evidence enough that it's correct. :)
Cheers.
\n\n
--
To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
FYI: filed as FreeBSD PR ports/132601.
Thanks for the great work guys. I had my doubts about lua in the
beginning but it has grown on me.
Cheers.
\n\n
--
To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
On Sun, Mar 01, 2009 at 09:00:39AM +0100, Julien Danjou wrote:
At 1235851721 time_t, Mariusz Ceier wrote:
We need to handle FocusIn event to update focused client, when
client with GAIM sends SetInputFocus message ( that is FocusIn event
for WM )
Pushed into 'next'.
Any chance of seeing
On Tue, Mar 03, 2009 at 04:22:24PM +0100, Julien Danjou wrote:
At 1236093422 time_t, Nikos Ntarmos wrote:
Any chance of seeing this in 3.2? Clients following the globally
active
focus model are seriously broken without these patches.
Why not. Can you name one?
JBidwatcher (and almost all
Hi all.
I just noticed that when changing from a screen with a focused client to
a screen with no clients on the active tab, then the focus remains on
the client on the first screen. This isn't bad per-se, but consider this
scenario:
* Screen 1, tag 1: client 1.
* Screen 2, tag 1: no
11 matches
Mail list logo
