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"
Þ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
On Sun, Jan 15, 2012 at 07:29:13AM +0100, Anselm R Garbe wrote:
> On 15 January 2012 07:27, Anselm R Garbe wrote:
> > On 15 January 2012 00:26, Ivan Kanakarakis wrote:
> >> On 15 January 2012 00:52, Andreas Amann wrote:
> >>> just to ask, do you happen to have the command "wmname LG3D" in your
>
On 15 January 2012 08:29, Anselm R Garbe wrote:
> On 15 January 2012 07:27, Anselm R Garbe wrote:
> > On 15 January 2012 00:26, Ivan Kanakarakis wrote:
> >> On 15 January 2012 00:52, Andreas Amann
> wrote:
> >>> just to ask, do you happen to have the command "wmname LG3D" in your
> >>> startup
On 15 January 2012 07:27, Anselm R Garbe wrote:
> On 15 January 2012 00:26, Ivan Kanakarakis wrote:
>> On 15 January 2012 00:52, Andreas Amann 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?
>>>
>
On 15 January 2012 00:26, Ivan Kanakarakis wrote:
> On 15 January 2012 00:52, Andreas Amann 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 "wmname LG3D"
> I'm not home right
On 15 January 2012 00:52, Andreas Amann wrote:
> On Mon, Jan 09, 2012 at 04:55:08PM +0200, Ivan Kanakarakis wrote:
> > On 9 January 2012 16:34, Ivan Kanakarakis wrote:
> >
> >
> >
> > ow, sorry, cross that out. I misread the question.
> > Even with the patch applied, the problem is still there.
On Mon, Jan 09, 2012 at 04:55:08PM +0200, Ivan Kanakarakis wrote:
> On 9 January 2012 16:34, Ivan Kanakarakis 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" .
> Sorry for
On 9 January 2012 16:34, Ivan Kanakarakis wrote:
>
>
> On 9 January 2012 01:12, Andreas Amann 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
On 9 January 2012 01:12, Andreas Amann 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 still exist with
>
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
On Sun, Jan 08, 2012 at 12:29:38PM +0100, Anselm R Garbe wrote:
> On 8 January 2012 02:03, Andreas Amann 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.
>
> Which kind o
On 8 January 2012 13:28, Anselm R Garbe wrote:
> On 7 January 2012 21:20, Ivan Kanakarakis 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 e
On 8 January 2012 02:03, Andreas Amann 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 id. That is ofcourse
On 7 January 2012 21:20, Ivan Kanakarakis 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 that:
>
>> [...] Th
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 t
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 Manager
17 matches
Mail list logo
