From: Michael Heerdegen <michael_heerdegen@web.de>
To: Drew Adams <drew.adams@oracle.com>
Cc: 17562@debbugs.gnu.org, Stephen Berman <stephen.berman@gmx.net>
Subject: bug#17562: 24.4.50; REGRESSION: mouse double-click on `(` does not select whole Lisp sexp
Date: Tue, 27 May 2014 00:25:03 +0200 [thread overview]
Message-ID: <878uponpog.fsf@web.de> (raw)
In-Reply-To: <8e3dd26e-4b72-422e-b288-79520a6eedcd@default> (Drew Adams's message of "Mon, 26 May 2014 15:01:40 -0700 (PDT)")
Drew Adams <drew.adams@oracle.com> writes:
> I don't see it with this build, so it seems to have been introduced
> between 4/29 and 5/17. Unfortunately, I have no build between those
> two, to check in more detail.
It seems to have been introduced by this commit:
44812aa45a823e344811f4f38966c3e5c9b5118f
Author: Stefan Monnier <monnier@iro.umontreal.ca>
Date: Sun May 11 01:49:14 2014 -0400
* lisp/mouse.el: Use the normal toplevel loop while dragging.
(mouse-set-point): Handle multi-clicks.
(mouse-set-region): Handle multi-clicks for drags.
(mouse-drag-region): Update call accordingly.
(mouse-drag-track): Remove `do-mouse-drag-region-post-process' hack.
Use the normal event loop instead of a local while/read-event loop.
(global-map): Remove redundant bindings for double/triple-mouse-1.
* lisp/xt-mouse.el (xterm-mouse-translate-1): Only process one event at a time.
Generate synthetic down events when the protocol only sends up events.
(xterm-mouse-last): Remove.
(xterm-mouse--read-event-sequence-1000): Use xterm-mouse-last-down
terminal parameter instead.
(xterm-mouse--set-click-count): New function.
(xterm-mouse-event): Detect/generate double/triple clicks.
* lisp/reveal.el (reveal-close-old-overlays): Don't close while
dragging.
Michael.
next prev parent reply other threads:[~2014-05-26 22:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 17:00 bug#17562: 24.4.50; REGRESSION: mouse double-click on `(` does not select whole Lisp sexp Drew Adams
2014-05-26 19:29 ` Drew Adams
2014-05-26 19:31 ` Drew Adams
2014-05-26 21:41 ` Stephen Berman
2014-05-26 22:01 ` Drew Adams
2014-05-26 22:25 ` Michael Heerdegen [this message]
2014-05-26 22:42 ` Michael Heerdegen
2014-05-26 22:54 ` Stefan Monnier
2014-05-27 0:38 ` Drew Adams
2014-05-27 0:55 ` Michael Heerdegen
2014-05-27 3:32 ` Stefan Monnier
2014-05-27 5:08 ` Stefan Monnier
2014-05-27 18:18 ` Michael Heerdegen
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=878uponpog.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=17562@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=stephen.berman@gmx.net \
/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).