Re: display-window/warp-to-window-enabled bugs
Daniel Pfeiffer <occitan <at> esperanto.org>
2002-12-02 20:32:06 GMT
John Harper <jsh <at> unfactored.org> skribis:
> On Sunday, Dec 1, 2002, at 04:48 US/Pacific, merlin wrote:
> > In recent sawfishen, warp-to-window-enabled defaults to
> > nil, so display-window (from cycling or the menu) will
> > focus windows without moving the pointer. This is pretty
> > unintuitive for focus-mode 'enter-exit and 'enter-only.
> My reasoning was that warping the pointer is always a bad idea, so I
> thought it should be disabled by default. There are already cases where
> the constraint that in focus follows mouse focus modes the pointer is
> always inside the focused window is broken, so adding another instance
> of this seemed better than forcing everyone using ffm modes to put up
> with the pointer being warped
Well, I for one had meant to report this as a bug, but was never quite bothered enough to sit down and write it. I
have ffm (focus-mode enter-only) and focus goes to new windows (focus-windows-when-mapped t). But even with
(setq warp-to-window-enabled t)
I get the startling focus-doesn't-follow-mouse situation where the pointer stays where it was, and if
that isn't where the new window pops up, that gets the focus but not the mouse.
While you seem aware of this, I've-done-it-wrong-once is no excuse for doing it wrong in another situation
rather than fixing the first. Ffm (that's short for Frankfurt am Main, btw. sometimes should imply
warping when combined with certain other options, and there's nothing wrong with that.
Now if you want to take warping away from the Kindergarden lot, then you must also take away everything that
then becomes inconsistent!
coralament / best Grötens / liebe Grüße / best regards / elkorajn salutojn