From: Eli Zaretskii <eliz@gnu.org>
To: monnier@IRO.UMontreal.CA
Cc: m43cap@yandex.com, 30955@debbugs.gnu.org
Subject: bug#30955: 27.0.50; Mouse clicks on header-line in Info are broken
Date: Sat, 31 Mar 2018 22:16:04 +0300 [thread overview]
Message-ID: <83tvsw6op7.fsf@gnu.org> (raw)
In-Reply-To: <83vadc6p9p.fsf@gnu.org> (message from Eli Zaretskii on Sat, 31 Mar 2018 22:03:46 +0300)
> Date: Sat, 31 Mar 2018 22:03:46 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 30955@debbugs.gnu.org, monnier@IRO.UMontreal.CA
>
> But just to be sure: can you describe the exact sequence of steps you
> are taking, starting from "emacs -Q"? In particular, are you clicking
> on the Next/Prev/Up links of the header-line in an Info buffer?
Btw, the keymap property we put on the header-line does bind mouse-2
to a command that follows link, not mouse-1:
(define-key keymap [header-line down-mouse-1] 'mouse-drag-header-line)
(define-key keymap [header-line mouse-1] 'mouse-select-window)
(define-key keymap [header-line mouse-2] 'Info-mouse-follow-link)
(define-key keymap [mouse-2] 'Info-mouse-follow-link)
(define-key keymap [follow-link] 'mouse-face)
So I guess this is somehow related to the processing of
mouse-1-click-follows-link.
next prev parent reply other threads:[~2018-03-31 19:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 14:54 bug#30955: 27.0.50; Mouse clicks on header-line in Info are broken Eli Zaretskii
2018-03-27 18:46 ` Stefan Monnier
2018-03-27 19:27 ` Stefan Monnier
2018-03-28 6:07 ` Colin Baxter
2018-03-29 11:00 ` Eli Zaretskii
2018-03-29 12:10 ` Stefan Monnier
2018-03-29 12:24 ` Eli Zaretskii
2018-03-29 13:11 ` Stefan Monnier
2018-03-29 13:30 ` Colin Baxter
2018-03-31 17:18 ` Eli Zaretskii
2018-03-31 18:56 ` Colin Baxter
2018-03-31 19:03 ` Eli Zaretskii
2018-03-31 19:16 ` Eli Zaretskii [this message]
2018-03-31 20:59 ` Colin Baxter
2018-03-31 20:55 ` Colin Baxter
2018-03-31 23:40 ` Stefan Monnier
2018-04-01 6:50 ` Eli Zaretskii
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=83tvsw6op7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=30955@debbugs.gnu.org \
--cc=m43cap@yandex.com \
--cc=monnier@IRO.UMontreal.CA \
/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.