RE: focus-follows-mouse should be nil by default on MS Windows

[Drew Adams]

    >     Anyway, I cannot see any difference in behavior of, say, "C-x 5 o"

    > Documenting that would seem to be wrong, as the example I
    > sent shows. In that example, if the value is nil, then the mouse
    > position does not get set; if non-nil, it gets set.

    Is this the example you are referring to?

Yes.

    If so, I must ask you: did you actually tried this code?  ("C-x 5 o"
    calls this function, so it would suffice to try that command.)

Yes, I use `C-x 5 o'.

    I did try it, with both nil and t as values of focus-follows-mouse,
    and I don't see _any_ change in behavior whatsoever.

You're right. I didn't test it with different values of the option.

    Which is what I'd
    expect, since AFAIU set-mouse-position is invoked for the case where
    without it the focus will stay in the original frame;

I see; you're right.

    this doesn't
    happen on Windows, at least not for me, and the documentation of the
    Windows API call invoked by w32-focus-frame seems to confirm that.

Dunno about the latter part. Do you mean just because the doc string says
"raising to foreground if necessary"? (What does "if necessary" mean here?)

    If you can show a precise recipe where this variable matters in some
    way, please do.

Nope, I don't have one. Sorry for the noise.

    FWIW, I think the name of the variable is misleading, to some extent:
    it was introduced to overcome a difficulty with certain window
    managers on X, but that difficulty is not really in the fact that
    focus follows the mouse pointer; rather, the focus policy is a
    _symptom_ of another problem which prevents Emacs from giving focus to
    the frame as part of x-focus-frame call.  I'm not an expert on X, so
    perhaps Jan or someone else could comment on what really happens on X
    wrt this.

It's sure that more than one person has been confused, based on the variable
name, but there's not much to be done about that now.