unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Nils Berg <nilsb@google.com>
To: 23288@debbugs.gnu.org
Subject: bug#23288: 25.0.92; Clicking on links inserts primary X selection
Date: Thu, 14 Apr 2016 19:14:40 +0200	[thread overview]
Message-ID: <CAGpFBBs-1CapH0nC3rFJG=QDygL_ASqQJbw+JMaKW_c5AQLoSA@mail.gmail.com> (raw)
In-Reply-To: <wvr4ziswfk37.fsf@a.muc.corp.google.com>

[-- Attachment #1: Type: text/plain, Size: 356 bytes --]

I've tracked down the bug to mouse--down-1-maybe-follows-link too, but
don't think read-event is the culprit here.

Rather, mouse--down-1-maybe-follows-link discards the result of
mouse-on-link-p, which contains the event a click is supposed to be
translated into. Instead, it just replaces the mouse event with mouse-2 if
mouse-on-link-p returns non-nil.

[-- Attachment #2: Type: text/html, Size: 410 bytes --]

  parent reply	other threads:[~2016-04-14 17:14 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-14 12:31 bug#23288: 25.0.92; Clicking on links inserts primary X selection Philipp Stephani
2016-04-14 15:33 ` Glenn Morris
2016-04-14 17:14 ` Nils Berg [this message]
2016-04-16 13:36   ` Philipp Stephani
2016-04-18  8:50     ` Nils Berg
2016-04-20 16:53       ` Philipp Stephani
2016-05-10 21:25         ` Philipp Stephani
2016-05-11  8:14           ` Eli Zaretskii
2016-05-11  8:32             ` Nils Berg
2016-05-11 13:01               ` Philipp Stephani
2016-05-11 13:14                 ` Nils Berg
2016-05-11 13:32             ` Philipp Stephani
2016-05-11 13:56               ` Eli Zaretskii
2016-05-11 18:18                 ` John Wiegley
2016-05-11 18:40                 ` Glenn Morris
2016-05-11 21:04                   ` Eli Zaretskii
2016-05-12  5:42                     ` John Wiegley
2016-05-12 19:26                       ` Eli Zaretskii
2016-05-12 21:24                         ` John Wiegley
2016-05-12 16:49                     ` Glenn Morris
2016-05-20 18:24             ` Philipp Stephani

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='CAGpFBBs-1CapH0nC3rFJG=QDygL_ASqQJbw+JMaKW_c5AQLoSA@mail.gmail.com' \
    --to=nilsb@google.com \
    --cc=23288@debbugs.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).