unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Bastien'" <bastienguerry@googlemail.com>
Cc: emacs-pretest-bug@gnu.org, 3931@emacsbugs.donarmstrong.com
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	[thread overview]
Message-ID: <D4E224B27EC84864B96E5DBBC41BD551@us.oracle.com> (raw)
In-Reply-To: <874osz9rlr.fsf@bzg.ath.cx>

> > 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.






  reply	other threads:[~2009-07-26 19:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-26 16:44 bug#3931: 23.0.96; doc of select-frame-set-input-focus and select-frame Drew Adams
2009-07-26 19:22 ` Bastien
2009-07-26 19:33   ` Drew Adams [this message]
2011-07-12 20:02 ` Lars Magne Ingebrigtsen
2011-07-12 21:11   ` Drew Adams
2012-01-29  5:23 ` Drew Adams

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D4E224B27EC84864B96E5DBBC41BD551@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=3931@emacsbugs.donarmstrong.com \
    --cc=bastienguerry@googlemail.com \
    --cc=emacs-pretest-bug@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).