From: Eli Zaretskii <eliz@gnu.org>
To: Colin Baxter <m43cap@yandex.com>
Cc: 30955@debbugs.gnu.org, monnier@IRO.UMontreal.CA
Subject: bug#30955: 27.0.50; Mouse clicks on header-line in Info are broken
Date: Sat, 31 Mar 2018 22:03:46 +0300 [thread overview]
Message-ID: <83vadc6p9p.fsf@gnu.org> (raw)
In-Reply-To: <87bmf4f50h.fsf@yandex.com> (message from Colin Baxter on Sat, 31 Mar 2018 19:56:30 +0100)
> From: Colin Baxter <m43cap@yandex.com>
> Cc: Stefan Monnier <monnier@IRO.UMontreal.CA>, 30955@debbugs.gnu.org
> Cc:
> Date: Sat, 31 Mar 2018 19:56:30 +0100
>
> > AFAICT, this patch is now installed on master, but I still see the
> > same issue: "C-h c" reports mouse-2 whereas I click mouse-1. Was
> > this issue supposed to be resolved, and if so, what am I missing?
>
> For me, C-h c gives mouse-1 for the left-hand button (mouse 1) and
> mouse-3 for the right-hand button (mouse 3).
Maybe it's a Windows-specific issue, then.
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?
next prev parent reply other threads:[~2018-03-31 19:03 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 [this message]
2018-03-31 19:16 ` Eli Zaretskii
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=83vadc6p9p.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.