From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Drew Adams <drew.adams@oracle.com>
Cc: 17562@debbugs.gnu.org
Subject: bug#17562: 24.4.50; REGRESSION: mouse double-click on `(` does not select whole Lisp sexp
Date: Mon, 26 May 2014 18:54:09 -0400 [thread overview]
Message-ID: <jwvppj0rwc3.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <28b9c286-b99c-42b1-9768-d39a449a9855@default> (Drew Adams's message of "Fri, 23 May 2014 10:00:17 -0700 (PDT)")
> Visit dired.el. Double-click on the opening paren of
> (defun dired-get-filename ...
> Only part of the defun is selected.
Hmm... I can't reproduce it here (using "emacs -Q"):
- after opening dired.el I first have to search for "defun dired-get-filename"
because it's not immediately visible.
- once it's in sight, if I double-click on it, the whole expression is
selected&highlighted, point is moved to right after the matching close
paren, and as a consequence the window is redrawn to show the end of
the expression (since the beginning is now outside of the window).
I never use this feature, but I see the exact same behavior in
Emacs-24.3, so I assume it's the way it's always worked.
Can you reproduce the problem with "emacs -Q"?
> 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.
Yes, it clearly the likely culprit.
Stefan
next prev parent reply other threads:[~2014-05-26 22:54 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
2014-05-26 22:42 ` Michael Heerdegen
2014-05-26 22:54 ` Stefan Monnier [this message]
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=jwvppj0rwc3.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=17562@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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).