On Sat, Jun 29, 2019 at 12:29:03AM -0400 I heard the voice of Stefan Monnier, and lo! it spake thus: > > FWIW, I think keeping the mouse pointer grabbed all the way until > the exec'd command terminates seems like an awful long time.
Well. Maybe... OTOH, remember that we also have ctwm frozen up all the way until the exec'd command terminates too. So even if that did cause some sort of problem, it would only be in the case that we exec something long-running, that somehow expects mouse actions we can't give it, but also doesn't need the WM to do anything like map or border it. That's a pretty edge case. And don't forget, ctwm didn't have it 'till 3.5. twm doesn't have it to this day. Neither does vtwm. The 3.5 diff is pretty big, so eye-reading with finite time is fraught. Still, I don't see anything leaping out at my that would obviously justify it. There are only 2 XGrabPointer's added in that diff; one is involved in moving windows, and the other is in f.hypermove. Neither would result in calling f.exec... Too, "Grab Pointer" isn't just the way we take over control of hearing mouse movements. It's also the mechanism by which we don't do any taking over at all, but just change the cursor shape. We do in fact XGrabPointer() early on in function dispatching (functions.c:216) for all but a few funcs just to set the stopwatch cursor. So, my guess is that there isn't any reason for it, and maybe never was. -- Matthew Fuller (MF4839) | [email protected] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.
