On Mon, Aug 3, 2009 at 4:13 PM, Colin Shea wrote:
> Have you looked at the man page for unclutter? There is an option
> (-noevents or some such thing) that makes unclutter not send any X11
> signals. This should fix your bug.
I had, but forgot to test out the different options before submitting
On Mon, Aug 03, 2009 at 09:13:28AM -0500, Colin Shea wrote:
>
> Have you looked at the man page for unclutter? There is an option
> (-noevents or some such thing) that makes unclutter not send any X11
> signals. This should fix your bug.
>
Thanks for the tip, I'm not experiencing the problem the
On Mon, Aug 03, 2009 at 09:56:40AM +0100, Anselm R Garbe wrote:
> Hi Eivind,
>
> thanks for your investigation. I looked through the code and
> remembered that unfocus() sets the input focus to the root window in
> order that clients are notified with FocusOut (in terminals this has
> the effect t
Hi Eivind,
thanks for your investigation. I looked through the code and
remembered that unfocus() sets the input focus to the root window in
order that clients are notified with FocusOut (in terminals this has
the effect that the cursor turns into unfocused state).
So in general there is nothing
After updating from 5.5 to 5.6 I encountered a bug relating to unclutter[1].
Steps to reproduse:
1. Start dwm 5.6 with default config and unclutter with default params.
2. Open more than one window in the active tag.
3. Wait until unclutter hides the cursor.
4. Switch to a window not focused by th
