[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#3931: 23.0.96; doc of select-frame-set-input-focus and select-frame
From: |
Drew Adams |
Subject: |
bug#3931: 23.0.96; doc of select-frame-set-input-focus and select-frame |
Date: |
Sun, 26 Jul 2009 12:33:38 -0700 |
> > Doc string of `select-frame-set-input-focus':
> > "If `mouse-autoselect-window' is non-nil, also move mouse cursor to
> > FRAME's selected window. Otherwise, if `focus-follows-mouse' is
> > non-nil, move mouse cursor to FRAME."
> >
> > Why "Otherwise"?
>
> Because the value of `focus-follows-mouse' is only checked if
> `mouse-autoselect-window' is nil.
OK, in that case the text is correct. But it could easily be misread by some
users. It would be clearer to state this explicitly: "If
`mouse-autoselect-window' is nil and `mouse-autoselect-window' is non-nil, then
move the mouse pointer to FRAME."
And it wouldn't hurt to state this explicitly also:
"Otherwise, do not move the mouse pointer."
> > Similar problems exist for the description in the Elisp manual (the
> > text is almost the same). In addition, the manual should say
> > something more about the differences between these two
> functions, and
> > mention when you might use one or the other.
>
> I don't know how to fix the Elisp manual.
Hopefully, someone else does. ;-)
Thx.