From ddeus.clfswm at mailnull.com  Sun Jan  6 11:47:43 2013
From: ddeus.clfswm at mailnull.com (Oleksandr Kozachuk)
Date: Sun, 06 Jan 2013 12:47:43 +0100
Subject: [clfswm-devel] Unmanaged window per default
Message-ID: <848d8840bad6fc5b188f21a6db110614@kozachuk.info>

Hi!

Firefox windows are not managed per default after some of last commits, 
at least for me. The evaluation of (never-managed-window-p 
(current-child)) returns nil on firefox window. So I have the general 
question, how can I configure which application should be per default 
managed and which not?

Best regards,
Oleksandr.



From ddeus.clfswm at mailnull.com  Sun Jan  6 12:45:06 2013
From: ddeus.clfswm at mailnull.com (Oleksandr Kozachuk)
Date: Sun, 06 Jan 2013 13:45:06 +0100
Subject: [clfswm-devel] Unmanaged window per default
In-Reply-To: <848d8840bad6fc5b188f21a6db110614@kozachuk.info>
References: <848d8840bad6fc5b188f21a6db110614@kozachuk.info>
Message-ID: <58363eee47fac4bbf00af0514ea52770@kozachuk.info>

Je 2013-01-06 12:47, Oleksandr Kozachuk skribis:
> Firefox windows are not managed per default after some of last
> commits, at least for me. The evaluation of (never-managed-window-p
> (current-child)) returns nil on firefox window. So I have the general
> question, how can I configure which application should be per default
> managed and which not?

So, I have found the answer, at least partly: firefox windows are
:maxsize windows, and put :maxsize to *default-managed-type* let it be
managed per default (or to (frame-managed-type ...) for particular
frame). But what is the reason for :maxsize type of all firefox
windows?

Best regards,
Oleksandr.




From pbrochard at common-lisp.net  Sun Jan  6 14:10:45 2013
From: pbrochard at common-lisp.net (Philippe Brochard)
Date: Sun, 06 Jan 2013 15:10:45 +0100
Subject: [clfswm-devel] Unmanaged window per default
In-Reply-To: <58363eee47fac4bbf00af0514ea52770@kozachuk.info> (Oleksandr
	Kozachuk's message of "Sun, 06 Jan 2013 13:45:06 +0100")
References: <848d8840bad6fc5b188f21a6db110614@kozachuk.info>
	<58363eee47fac4bbf00af0514ea52770@kozachuk.info>
Message-ID: <87fw2ejtay.fsf@common-lisp.net>

Oleksandr Kozachuk writes:

> Je 2013-01-06 12:47, Oleksandr Kozachuk skribis:
>> Firefox windows are not managed per default after some of last
>> commits, at least for me. The evaluation of (never-managed-window-p
>> (current-child)) returns nil on firefox window. So I have the general
>> question, how can I configure which application should be per default
>> managed and which not?
>
> So, I have found the answer, at least partly: firefox windows are
> :maxsize windows, and put :maxsize to *default-managed-type* let it be
> managed per default (or to (frame-managed-type ...) for particular
> frame). But what is the reason for :maxsize type of all firefox
> windows?
>
Hi. On my box firefox (10.0.11) windows are normal windows. What is your
firefox version? Do you use the last git clfswm version?

Best regards,

Philippe



From ales.guzik at gmail.com  Sun Jan  6 14:16:42 2013
From: ales.guzik at gmail.com (Ales Guzik)
Date: Sun, 6 Jan 2013 16:16:42 +0200
Subject: [clfswm-devel] Unmanaged window per default
In-Reply-To: <87fw2ejtay.fsf@common-lisp.net>
References: <848d8840bad6fc5b188f21a6db110614@kozachuk.info>
	<58363eee47fac4bbf00af0514ea52770@kozachuk.info>
	<87fw2ejtay.fsf@common-lisp.net>
Message-ID: <CADT2y-06xR4OWvuHTWqTNg4ewupqbUK90W98R0Nx9XD5NwNZMg@mail.gmail.com>

Hi

It became maxsize somewhere near firefox 16. Current firefox is 17 or 18. I
also have maxsize added to default-managed.

Ales
On 6 Jan 2013 17:10, "Philippe Brochard" <pbrochard at common-lisp.net> wrote:

> Oleksandr Kozachuk writes:
>
> > Je 2013-01-06 12:47, Oleksandr Kozachuk skribis:
> >> Firefox windows are not managed per default after some of last
> >> commits, at least for me. The evaluation of (never-managed-window-p
> >> (current-child)) returns nil on firefox window. So I have the general
> >> question, how can I configure which application should be per default
> >> managed and which not?
> >
> > So, I have found the answer, at least partly: firefox windows are
> > :maxsize windows, and put :maxsize to *default-managed-type* let it be
> > managed per default (or to (frame-managed-type ...) for particular
> > frame). But what is the reason for :maxsize type of all firefox
> > windows?
> >
> Hi. On my box firefox (10.0.11) windows are normal windows. What is your
> firefox version? Do you use the last git clfswm version?
>
> Best regards,
>
> Philippe
>
> _______________________________________________
> clfswm-devel mailing list
> clfswm-devel at common-lisp.net
> http://lists.common-lisp.net/cgi-bin/mailman/listinfo/clfswm-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/clfswm-devel/attachments/20130106/68677fbc/attachment.html>

From pbrochard at common-lisp.net  Sun Jan  6 14:36:32 2013
From: pbrochard at common-lisp.net (Philippe Brochard)
Date: Sun, 06 Jan 2013 15:36:32 +0100
Subject: [clfswm-devel] Unmanaged window per default
In-Reply-To: <CADT2y-06xR4OWvuHTWqTNg4ewupqbUK90W98R0Nx9XD5NwNZMg@mail.gmail.com>
	(Ales Guzik's message of "Sun, 6 Jan 2013 16:16:42 +0200")
References: <848d8840bad6fc5b188f21a6db110614@kozachuk.info>
	<58363eee47fac4bbf00af0514ea52770@kozachuk.info>
	<87fw2ejtay.fsf@common-lisp.net>
	<CADT2y-06xR4OWvuHTWqTNg4ewupqbUK90W98R0Nx9XD5NwNZMg@mail.gmail.com>
Message-ID: <87bod2js3z.fsf@common-lisp.net>

Ales Guzik writes:

> Hi
>
> It became maxsize somewhere near firefox 16. Current firefox is 17 or 18. I
> also have maxsize added to default-managed.
>
Ok, I have added (commit 695078a) maxsize windows in *default-managed-type*
since there is the same problem with audacity.
But we'll have to detach zynaddsubfx manually now :-)

Regards,

Philippe

> Ales
>
> On 6 Jan 2013 17:10, "Philippe Brochard" <pbrochard at common-lisp.net> wrote:
>
>     Oleksandr Kozachuk writes:
>
>     > Je 2013-01-06 12:47, Oleksandr Kozachuk skribis:
>     >> Firefox windows are not managed per default after some of last
>     >> commits, at least for me. The evaluation of (never-managed-window-p
>     >> (current-child)) returns nil on firefox window. So I have the general
>     >> question, how can I configure which application should be per default
>     >> managed and which not?
>     >
>     > So, I have found the answer, at least partly: firefox windows are
>     > :maxsize windows, and put :maxsize to *default-managed-type* let it be
>     > managed per default (or to (frame-managed-type ...) for particular
>     > frame). But what is the reason for :maxsize type of all firefox
>     > windows?
>     >
>     Hi. On my box firefox (10.0.11) windows are normal windows. What is your
>     firefox version? Do you use the last git clfswm version?
>
>     Best regards,
>
>     Philippe
>
>     _______________________________________________
>     clfswm-devel mailing list
>     clfswm-devel at common-lisp.net
>     http://lists.common-lisp.net/cgi-bin/mailman/listinfo/clfswm-devel
>
> _______________________________________________
> clfswm-devel mailing list
> clfswm-devel at common-lisp.net
> http://lists.common-lisp.net/cgi-bin/mailman/listinfo/clfswm-devel



From oleksandr at kozachuk.info  Sun Jan  6 14:30:53 2013
From: oleksandr at kozachuk.info (Oleksandr Kozachuk)
Date: Sun, 06 Jan 2013 15:30:53 +0100
Subject: [clfswm-devel] Unmanaged window per default
In-Reply-To: <87fw2ejtay.fsf@common-lisp.net>
References: <848d8840bad6fc5b188f21a6db110614@kozachuk.info>
	<58363eee47fac4bbf00af0514ea52770@kozachuk.info>
	<87fw2ejtay.fsf@common-lisp.net>
Message-ID: <816122f3e0003ca44ff6eb1dece6edd5@kozachuk.info>

Je 2013-01-06 15:10, Philippe Brochard skribis:
> Oleksandr Kozachuk writes:
>> Je 2013-01-06 12:47, Oleksandr Kozachuk skribis:
>>> Firefox windows are not managed per default after some of last
>>> commits, at least for me. The evaluation of (never-managed-window-p
>>> (current-child)) returns nil on firefox window. So I have the 
>>> general
>>> question, how can I configure which application should be per 
>>> default
>>> managed and which not?
>> So, I have found the answer, at least partly: firefox windows are
>> :maxsize windows, and put :maxsize to *default-managed-type* let it 
>> be
>> managed per default (or to (frame-managed-type ...) for particular
>> frame). But what is the reason for :maxsize type of all firefox
>> windows?
> Hi. On my box firefox (10.0.11) windows are normal windows. What is 
> your
> firefox version? Do you use the last git clfswm version?

I have Firefox 17.0 and last clfswm version.

Best regards,
Oleksandr.




From ddeus.clfswm at mailnull.com  Sun Jan  6 14:47:48 2013
From: ddeus.clfswm at mailnull.com (Oleksandr Kozachuk)
Date: Sun, 06 Jan 2013 15:47:48 +0100
Subject: [clfswm-devel] Unmanaged window per default
In-Reply-To: <816122f3e0003ca44ff6eb1dece6edd5@kozachuk.info>
References: <848d8840bad6fc5b188f21a6db110614@kozachuk.info>
	<58363eee47fac4bbf00af0514ea52770@kozachuk.info>
	<87fw2ejtay.fsf@common-lisp.net>
	<816122f3e0003ca44ff6eb1dece6edd5@kozachuk.info>
Message-ID: <a851bd8251a81820f6f882be9a15a728@kozachuk.info>

Je 2013-01-06 15:30, Oleksandr Kozachuk skribis:
> Je 2013-01-06 15:10, Philippe Brochard skribis:
>> Oleksandr Kozachuk writes:
>>> Je 2013-01-06 12:47, Oleksandr Kozachuk skribis:
>>>> Firefox windows are not managed per default after some of last
>>>> commits, at least for me. The evaluation of (never-managed-window-p
>>>> (current-child)) returns nil on firefox window. So I have the 
>>>> general
>>>> question, how can I configure which application should be per 
>>>> default
>>>> managed and which not?
>>> So, I have found the answer, at least partly: firefox windows are
>>> :maxsize windows, and put :maxsize to *default-managed-type* let it 
>>> be
>>> managed per default (or to (frame-managed-type ...) for particular
>>> frame). But what is the reason for :maxsize type of all firefox
>>> windows?
>> Hi. On my box firefox (10.0.11) windows are normal windows. What is 
>> your
>> firefox version? Do you use the last git clfswm version?
> I have Firefox 17.0 and last clfswm version.

The problem is, that max-width and max-height in wm-normal-hints is
set to 1073741824 for firefox windows and window-type returns :maxsize
therefore.

Best regards,
Oleksandr.




From pbrochard at common-lisp.net  Sun Jan  6 15:13:58 2013
From: pbrochard at common-lisp.net (Philippe Brochard)
Date: Sun, 06 Jan 2013 16:13:58 +0100
Subject: [clfswm-devel] Unmanaged window per default
In-Reply-To: <a851bd8251a81820f6f882be9a15a728@kozachuk.info> (Oleksandr
	Kozachuk's message of "Sun, 06 Jan 2013 15:47:48 +0100")
References: <848d8840bad6fc5b188f21a6db110614@kozachuk.info>
	<58363eee47fac4bbf00af0514ea52770@kozachuk.info>
	<87fw2ejtay.fsf@common-lisp.net>
	<816122f3e0003ca44ff6eb1dece6edd5@kozachuk.info>
	<a851bd8251a81820f6f882be9a15a728@kozachuk.info>
Message-ID: <877gnqjqdl.fsf@common-lisp.net>

Oleksandr Kozachuk writes:

> Je 2013-01-06 15:30, Oleksandr Kozachuk skribis:
>> Je 2013-01-06 15:10, Philippe Brochard skribis:
>>> Oleksandr Kozachuk writes:
>>>> Je 2013-01-06 12:47, Oleksandr Kozachuk skribis:
>>>>> Firefox windows are not managed per default after some of last
>>>>> commits, at least for me. The evaluation of (never-managed-window-p
>>>>> (current-child)) returns nil on firefox window. So I have the
>>>>> general
>>>>> question, how can I configure which application should be per
>>>>> default
>>>>> managed and which not?
>>>> So, I have found the answer, at least partly: firefox windows are
>>>> :maxsize windows, and put :maxsize to *default-managed-type* let
>>>> it be
>>>> managed per default (or to (frame-managed-type ...) for particular
>>>> frame). But what is the reason for :maxsize type of all firefox
>>>> windows?
>>> Hi. On my box firefox (10.0.11) windows are normal windows. What is
>>> your
>>> firefox version? Do you use the last git clfswm version?
>> I have Firefox 17.0 and last clfswm version.
>
> The problem is, that max-width and max-height in wm-normal-hints is
> set to 1073741824 for firefox windows and window-type returns :maxsize
> therefore.
>
Ok, so the fix in commit 6a451c6 is much more relevant. No more problems
between firefox/audacity and zynaddsubfx.
Thanks for the report. Also the function display-current-window-info
(second mode+w+i) will display window normal hints. This can be useful.

Best regards,

Philippe



From oleksandr at kozachuk.info  Sun Jan  6 15:51:20 2013
From: oleksandr at kozachuk.info (Oleksandr Kozachuk)
Date: Sun, 06 Jan 2013 16:51:20 +0100
Subject: [clfswm-devel] Unmanaged window per default
In-Reply-To: <877gnqjqdl.fsf@common-lisp.net>
References: <848d8840bad6fc5b188f21a6db110614@kozachuk.info>
	<58363eee47fac4bbf00af0514ea52770@kozachuk.info>
	<87fw2ejtay.fsf@common-lisp.net>
	<816122f3e0003ca44ff6eb1dece6edd5@kozachuk.info>
	<a851bd8251a81820f6f882be9a15a728@kozachuk.info>
	<877gnqjqdl.fsf@common-lisp.net>
Message-ID: <f47e243bc4e2571a7dbc85ae3667af11@kozachuk.info>

Je 2013-01-06 16:13, Philippe Brochard skribis:
> Ok, so the fix in commit 6a451c6 is much more relevant. No more 
> problems
> between firefox/audacity and zynaddsubfx.
> Thanks for the report. Also the function display-current-window-info
> (second mode+w+i) will display window normal hints. This can be 
> useful.

Thank you for the patch, it works very good!

Best regards,
Oleksandr.




From pbrochard at common-lisp.net  Sun Jan  6 16:24:27 2013
From: pbrochard at common-lisp.net (Philippe Brochard)
Date: Sun, 06 Jan 2013 17:24:27 +0100
Subject: [clfswm-devel] Unmanaged window per default
In-Reply-To: <f47e243bc4e2571a7dbc85ae3667af11@kozachuk.info> (Oleksandr
	Kozachuk's message of "Sun, 06 Jan 2013 16:51:20 +0100")
References: <848d8840bad6fc5b188f21a6db110614@kozachuk.info>
	<58363eee47fac4bbf00af0514ea52770@kozachuk.info>
	<87fw2ejtay.fsf@common-lisp.net>
	<816122f3e0003ca44ff6eb1dece6edd5@kozachuk.info>
	<a851bd8251a81820f6f882be9a15a728@kozachuk.info>
	<877gnqjqdl.fsf@common-lisp.net>
	<f47e243bc4e2571a7dbc85ae3667af11@kozachuk.info>
Message-ID: <87ehhyxosk.fsf@common-lisp.net>

Oleksandr Kozachuk writes:

> Je 2013-01-06 16:13, Philippe Brochard skribis:
>> Ok, so the fix in commit 6a451c6 is much more relevant. No more
>> problems
>> between firefox/audacity and zynaddsubfx.
>> Thanks for the report. Also the function display-current-window-info
>> (second mode+w+i) will display window normal hints. This can be
>> useful.
>
> Thank you for the patch, it works very good!
>
Again, thanks for your feedback. This bug is annoying me with audacity
for a while but I haven't take time to investigate on a fix.

Best regards,

Philippe



From ddeus.clfswm at mailnull.com  Tue Jan 15 09:22:59 2013
From: ddeus.clfswm at mailnull.com (Oleksandr Kozachuk)
Date: Tue, 15 Jan 2013 10:22:59 +0100
Subject: [clfswm-devel] Window name box bottom on the screen does not
	disappear
Message-ID: <23e5657114c4a6536664d31705f4f0f9@kozachuk.info>

Hi!

I have a problem, that the box, which appears on changing windows and
shows the window name, often does not disappear, but rests on the
screen as black box on top of windows. It also depends on the
application running, for example it happens mostly for firefox and
urxvt windows. I have attached some screenshots.

Any ideas?

Best regards,
Oleksandr.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: screenshot1.jpg
Type: image/jpeg
Size: 7566 bytes
Desc: not available
URL: <https://mailman.common-lisp.net/pipermail/clfswm-devel/attachments/20130115/6518d936/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: screenshot2.jpg
Type: image/jpeg
Size: 9869 bytes
Desc: not available
URL: <https://mailman.common-lisp.net/pipermail/clfswm-devel/attachments/20130115/6518d936/attachment-0001.jpg>

From pbrochard at common-lisp.net  Tue Jan 15 22:43:48 2013
From: pbrochard at common-lisp.net (Philippe Brochard)
Date: Tue, 15 Jan 2013 23:43:48 +0100
Subject: [clfswm-devel] Window name box bottom on the screen does not
	disappear
In-Reply-To: <23e5657114c4a6536664d31705f4f0f9@kozachuk.info> (Oleksandr
	Kozachuk's message of "Tue, 15 Jan 2013 10:22:59 +0100")
References: <23e5657114c4a6536664d31705f4f0f9@kozachuk.info>
Message-ID: <87ip6yjcd7.fsf@common-lisp.net>

Oleksandr Kozachuk writes:

> Hi!
>
Hi,

> I have a problem, that the box, which appears on changing windows and
> shows the window name, often does not disappear, but rests on the
> screen as black box on top of windows. It also depends on the
> application running, for example it happens mostly for firefox and
> urxvt windows. I have attached some screenshots.
>
I have seen this also.

> Any ideas?
>
A bad unwind-protect somewhere for the second mode. I'll have a look.

> Best regards,
>
Best regards,

> Oleksandr.
>
Philippe



From ddeus.clfswm at mailnull.com  Mon Jan 28 11:15:58 2013
From: ddeus.clfswm at mailnull.com (Oleksandr Kozachuk)
Date: Mon, 28 Jan 2013 12:15:58 +0100
Subject: [clfswm-devel] Window name box bottom on the screen does not
In-Reply-To: <87ip6yjcd7.fsf@common-lisp.net>
References: <23e5657114c4a6536664d31705f4f0f9@kozachuk.info>
	<87ip6yjcd7.fsf@common-lisp.net>
Message-ID: <20130128111557.GB12931@bohrium.kozachuk.info>

Hi!

is it possible to remove the box, at least, or close it manually?
How can i delete it in a running clfswm?

Best regards,
Oleksandr.

On Tue, Jan 15, 2013 at 11:43:48PM +0100, Philippe Brochard wrote:
> Oleksandr Kozachuk writes:
> 
> > Hi!
> >
> Hi,
> 
> > I have a problem, that the box, which appears on changing windows and
> > shows the window name, often does not disappear, but rests on the
> > screen as black box on top of windows. It also depends on the
> > application running, for example it happens mostly for firefox and
> > urxvt windows. I have attached some screenshots.
> >
> I have seen this also.
> 
> > Any ideas?
> >
> A bad unwind-protect somewhere for the second mode. I'll have a look.
> 
> > Best regards,
> >
> Best regards,
> 
> > Oleksandr.
> >
> Philippe
> 
> _______________________________________________
> clfswm-devel mailing list
> clfswm-devel at common-lisp.net
> http://lists.common-lisp.net/cgi-bin/mailman/listinfo/clfswm-devel
> 



From pbrochard at common-lisp.net  Mon Jan 28 16:11:40 2013
From: pbrochard at common-lisp.net (Philippe Brochard)
Date: Mon, 28 Jan 2013 17:11:40 +0100
Subject: [clfswm-devel] Window name box bottom on the screen does not
In-Reply-To: <20130128111557.GB12931@bohrium.kozachuk.info> (Oleksandr
	Kozachuk's message of "Mon, 28 Jan 2013 12:15:58 +0100")
References: <23e5657114c4a6536664d31705f4f0f9@kozachuk.info>
	<87ip6yjcd7.fsf@common-lisp.net>
	<20130128111557.GB12931@bohrium.kozachuk.info>
Message-ID: <871ud5p9s3.fsf@common-lisp.net>

Oleksandr Kozachuk writes:

> Hi!
>
Hi,

> is it possible to remove the box, at least, or close it manually?
> How can i delete it in a running clfswm?
>
You can evaluate the 'circulate-leave-function' from the REPL prompt
(don't know if this works from the clfswm REPL. I'll be better from the
slime REPL).

As you seem to see this bug quite often, can you also post the content
of variables *circulate-window* and *current-event-mode* before closing
the window name box.

I'm trying to watch what's going wrong.

Best regards,

Philippe

   

> Best regards,
> Oleksandr.
>
> On Tue, Jan 15, 2013 at 11:43:48PM +0100, Philippe Brochard wrote:
>> Oleksandr Kozachuk writes:
>> 
>> > Hi!
>> >
>> Hi,
>> 
>> > I have a problem, that the box, which appears on changing windows and
>> > shows the window name, often does not disappear, but rests on the
>> > screen as black box on top of windows. It also depends on the
>> > application running, for example it happens mostly for firefox and
>> > urxvt windows. I have attached some screenshots.
>> >
>> I have seen this also.
>> 
>> > Any ideas?
>> >
>> A bad unwind-protect somewhere for the second mode. I'll have a look.
>> 
>> > Best regards,
>> >
>> Best regards,
>> 
>> > Oleksandr.
>> >
>> Philippe
>> 
>> _______________________________________________
>> clfswm-devel mailing list
>> clfswm-devel at common-lisp.net
>> http://lists.common-lisp.net/cgi-bin/mailman/listinfo/clfswm-devel
>> 
>
> _______________________________________________
> clfswm-devel mailing list
> clfswm-devel at common-lisp.net
> http://lists.common-lisp.net/cgi-bin/mailman/listinfo/clfswm-devel



From ddeus.clfswm at mailnull.com  Tue Jan 29 13:12:24 2013
From: ddeus.clfswm at mailnull.com (Oleksandr Kozachuk)
Date: Tue, 29 Jan 2013 14:12:24 +0100
Subject: [clfswm-devel] Window name box bottom on the screen does not
In-Reply-To: <871ud5p9s3.fsf@common-lisp.net>
References: <23e5657114c4a6536664d31705f4f0f9@kozachuk.info>
	<87ip6yjcd7.fsf@common-lisp.net>
	<20130128111557.GB12931@bohrium.kozachuk.info>
	<871ud5p9s3.fsf@common-lisp.net>
Message-ID: <20130129131224.GA17219@bohrium.kozachuk.info>

On Mon, Jan 28, 2013 at 05:11:40PM +0100, Philippe Brochard wrote:
> Oleksandr Kozachuk writes:
> > is it possible to remove the box, at least, or close it manually?
> > How can i delete it in a running clfswm?
> You can evaluate the 'circulate-leave-function' from the REPL prompt
> (don't know if this works from the clfswm REPL. I'll be better from the
> slime REPL).
It does not help, because *circulate-window* is nil. How can i close a
window, when i only know his id?

Best regards,
Oleksandr.



From pbrochard at common-lisp.net  Tue Jan 29 13:38:29 2013
From: pbrochard at common-lisp.net (Philippe Brochard)
Date: Tue, 29 Jan 2013 14:38:29 +0100
Subject: [clfswm-devel] Window name box bottom on the screen does not
In-Reply-To: <20130129131224.GA17219@bohrium.kozachuk.info> (Oleksandr
	Kozachuk's message of "Tue, 29 Jan 2013 14:12:24 +0100")
References: <23e5657114c4a6536664d31705f4f0f9@kozachuk.info>
	<87ip6yjcd7.fsf@common-lisp.net>
	<20130128111557.GB12931@bohrium.kozachuk.info>
	<871ud5p9s3.fsf@common-lisp.net>
	<20130129131224.GA17219@bohrium.kozachuk.info>
Message-ID: <87pq0o2joq.fsf@common-lisp.net>

Oleksandr Kozachuk writes:

> On Mon, Jan 28, 2013 at 05:11:40PM +0100, Philippe Brochard wrote:
>> Oleksandr Kozachuk writes:
>> > is it possible to remove the box, at least, or close it manually?
>> > How can i delete it in a running clfswm?
>> You can evaluate the 'circulate-leave-function' from the REPL prompt
>> (don't know if this works from the clfswm REPL. I'll be better from the
>> slime REPL).
> It does not help, because *circulate-window* is nil. How can i close a
> window, when i only know his id?
>
Sure it helps me to see that the circulate-leave-function seems to be
called normally but the window is not destroyed. Sad!

Perhaps you can use xkill to kill it explicitly but I don't like this
solution since we must fix the bug in clfswm.

Please, can you recompile clfswm with xlib-debug enabled and send the
output here:

Put a '(pushnew :xlib-debug *features*)' at the REPL or in load.lisp
before recompiling clfswm.

Best regards,

Philippe