From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Matthew Woodcraft <matthew@woodcraft.me.uk>
Cc: 18212@debbugs.gnu.org
Subject: bug#18212: 24.3.92; Left-click on a button is treated as mouse-2
Date: Thu, 07 Aug 2014 22:28:38 -0400 [thread overview]
Message-ID: <jwvoavvwweb.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <20140807210228.GA11175@golux.woodcraft.me.uk> (Matthew Woodcraft's message of "Thu, 7 Aug 2014 22:02:28 +0100")
> Is that the right place for the workaround? The problem happens for any
> link, not just those in info mode.
Good question.
> Maybe there's some way to behave more like 24.3, where (as far as I can
> make out from describe-key output) left-click on a link gives
> down-mouse-1 followed by mouse-2?
24.3 indeed does not go through down-mouse-2 (because the implementation is
based on a "normal" binding of down-mouse-1 rather than a key-remapping
of down-mouse-1).
So maybe you're right here. Hmm...
> (This issue isn't causing me any problems; I'm just testing the pretest.
> I had imenu bound to down-mouse-2 because it's slightly more responsive
> than mouse-2, and left-clicking to follow links stopped working
> altogether until I found out what was responsible. So I suppose it might
> cause trouble for other people when they upgrade.)
Indeed things like imenu are better bound to down-mouse-2 than to mouse-2.
I'll sleep on it and try to remember to come back to it tomorrow,
Stefan
next prev parent reply other threads:[~2014-08-08 2:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 20:35 bug#18212: 24.3.92; Left-click on a button is treated as mouse-2 Matthew Woodcraft
2014-08-06 23:59 ` Glenn Morris
2014-08-07 13:08 ` Stefan Monnier
2014-08-07 18:36 ` Stefan Monnier
2014-08-07 21:02 ` Matthew Woodcraft
2014-08-08 2:28 ` Stefan Monnier [this message]
2014-08-08 18:38 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvoavvwweb.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=18212@debbugs.gnu.org \
--cc=matthew@woodcraft.me.uk \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.