From: Richard Stallman <rms@gnu.org>
To: Sean O'Rourke <sorourke@cs.ucsd.edu>
Cc: emacs-devel@gnu.org
Subject: Re: mouse-1-click-in-non-selected-windows
Date: Sun, 04 Mar 2007 21:55:48 -0500 [thread overview]
Message-ID: <E1HO3Ma-0002lT-Ap@fencepost.gnu.org> (raw)
In-Reply-To: <m2649mlz36.fsf@cs.ucsd.edu> (message from Sean O'Rourke on Wed, 28 Feb 2007 14:03:09 -0800)
I believe this change is necessary to make
mouse-1-click-in-non-selected-windows consistent with
mouse-1-click-follows-link when the latter is set to nil (which
is the case later around line 919).
What evidence is there that this change is needed?
Both of the callers of mouse mouse-on-link-p
test mouse-1-click-follows-link first.
next prev parent reply other threads:[~2007-03-05 2:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-28 22:03 mouse-1-click-in-non-selected-windows Sean O'Rourke
2007-03-05 2:55 ` Richard Stallman [this message]
2007-03-05 17:35 ` mouse-1-click-in-non-selected-windows Sean O'Rourke
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=E1HO3Ma-0002lT-Ap@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=sorourke@cs.ucsd.edu \
/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).