> I'd suggest commenting out the Ungrab call and running with it. See
> what happens :)
FWIW, I think keeping the mouse pointer grabbed all the way until the
exec'd command terminates seems like an awful long time.
I guess it can be worked around by running the command with an "&" so we
On Fri, Jun 28, 2019 at 09:48:26AM +0200 I heard the voice of
Frank Steiner, and lo! it spake thus:
>
> So currently it's not possible to use f.exec for any kind of mouse
> button binding, right? f.exec would need to know if the ungrab is
> neccessary or not but I guess it can't.
>
> Do you
Matthew D. Fuller wrote:
Ah! This turns out to be the key. It doesn't have to do with the
key+button; it has to do with f.exec. Bind it to just Button1, it'll
act the same.
Ah, I see!
It appears to be because of the XUngrabPointer() call in the f.exec
handler (functions_misc.c:347 in
