On 15 January 2012 08:29, Anselm R Garbe garb...@gmail.com wrote:
On 15 January 2012 07:27, Anselm R Garbe garb...@gmail.com wrote:
On 15 January 2012 00:26, Ivan Kanakarakis ivan.ka...@gmail.com wrote:
On 15 January 2012 00:52, Andreas Amann am...@physik.tu-berlin.de
wrote:
just to ask,
On Sun, Jan 15, 2012 at 07:29:13AM +0100, Anselm R Garbe wrote:
On 15 January 2012 07:27, Anselm R Garbe garb...@gmail.com wrote:
On 15 January 2012 00:26, Ivan Kanakarakis ivan.ka...@gmail.com wrote:
On 15 January 2012 00:52, Andreas Amann am...@physik.tu-berlin.de wrote:
just to ask, do
Þann sun 15.jan 2012 18:09, skrifaði Andreas Amann:
The problem is that Ivan uses wmname to set _NET_WM_NAME to LG3D.
Actually chromium does not care about _NET_WM_NAME. But wmname has a
dirty side effect, it sets the _NET_SUPPORTING_WM_CHECK property of the root
window to the window id of the
On Sun, Jan 15, 2012 at 06:18:03PM +, Bjartur Thorlacius wrote:
Should we not patch wmname?
As wmname is a hack for broken apps, they will probably break if you
try to fix it.
If you only need to set _NET_WM_NAME, you can also try
xprop -root -f _NET_WM_NAME 8s -set _NET_WM_NAME LG3D
On Mon, Jan 09, 2012 at 04:55:08PM +0200, Ivan Kanakarakis wrote:
On 9 January 2012 16:34, Ivan Kanakarakis ivan.ka...@gmail.com wrote:
ow, sorry, cross that out. I misread the question.
Even with the patch applied, the problem is still there.
What I meant was, nope, it doesn't fix it .
On 15 January 2012 00:52, Andreas Amann am...@physik.tu-berlin.de wrote:
On Mon, Jan 09, 2012 at 04:55:08PM +0200, Ivan Kanakarakis wrote:
On 9 January 2012 16:34, Ivan Kanakarakis ivan.ka...@gmail.com wrote:
ow, sorry, cross that out. I misread the question.
Even with the patch
On 15 January 2012 00:26, Ivan Kanakarakis ivan.ka...@gmail.com wrote:
On 15 January 2012 00:52, Andreas Amann am...@physik.tu-berlin.de wrote:
just to ask, do you happen to have the command wmname LG3D in your
startup
script or anything else which changes _NET_WM_NAME?
I actually do have
On 15 January 2012 07:27, Anselm R Garbe garb...@gmail.com wrote:
On 15 January 2012 00:26, Ivan Kanakarakis ivan.ka...@gmail.com wrote:
On 15 January 2012 00:52, Andreas Amann am...@physik.tu-berlin.de wrote:
just to ask, do you happen to have the command wmname LG3D in your
startup
script
On 9 January 2012 01:12, Andreas Amann am...@physik.tu-berlin.de wrote:
On Sun, Jan 08, 2012 at 01:50:35PM +0200, Ivan Kanakarakis wrote:
The patch attached to Andreas responce does that
and also adds support for _NET_CLIENT_LIST
Just to ask, does your other focus problem with Chromium
On 9 January 2012 16:34, Ivan Kanakarakis ivan.ka...@gmail.com wrote:
On 9 January 2012 01:12, Andreas Amann am...@physik.tu-berlin.de wrote:
On Sun, Jan 08, 2012 at 01:50:35PM +0200, Ivan Kanakarakis wrote:
The patch attached to Andreas responce does that
and also adds support for
On 7 January 2012 21:20, Ivan Kanakarakis ivan.ka...@gmail.com wrote:
I was going looking through dwm's code cause I've been having problems with
my own implementation of _NET_ACTIVE_WINDOW support for mosnterwm, and
noticed some things.
1) The ewmh standard on _NET_ACTIVE_WINDOW [0] says
On 8 January 2012 02:03, Andreas Amann am...@physik.tu-berlin.de wrote:
On Sat, Jan 07, 2012 at 10:20:27PM +0200, Ivan Kanakarakis wrote:
dwm, when it receives a _NET_ACTIVE_WINDOW message, it transfers focus to
the client that asked for it, but never sets the root window id to that
window's
On 8 January 2012 13:28, Anselm R Garbe garb...@gmail.com wrote:
On 7 January 2012 21:20, Ivan Kanakarakis ivan.ka...@gmail.com wrote:
I was going looking through dwm's code cause I've been having problems
with
my own implementation of _NET_ACTIVE_WINDOW support for mosnterwm, and
noticed
On Sun, Jan 08, 2012 at 12:29:38PM +0100, Anselm R Garbe wrote:
On 8 January 2012 02:03, Andreas Amann am...@physik.tu-berlin.de wrote:
I use the attached patch for this. In addition it also maintains a
NetClientList, which exposes the list of managed windows in the ewmh
recommended way.
On Sun, Jan 08, 2012 at 01:50:35PM +0200, Ivan Kanakarakis wrote:
The patch attached to Andreas responce does that
and also adds support for _NET_CLIENT_LIST
Just to ask, does your other focus problem with Chromium still exist with
that patch applied?
Andreas
Hi all,
I was going looking through dwm's code cause I've been having problems with
my own implementation of _NET_ACTIVE_WINDOW support for mosnterwm, and
noticed some things.
1) The ewmh standard on _NET_ACTIVE_WINDOW [0] says that:
[...] This is a read-only property set by the Window
On Sat, Jan 07, 2012 at 10:20:27PM +0200, Ivan Kanakarakis wrote:
dwm, when it receives a _NET_ACTIVE_WINDOW message, it transfers focus to
the client that asked for it, but never sets the root window id to that
window's id. That is ofcourse a choice - the standard doesn't force one to
do
17 matches
Mail list logo
