From: Colin Baxter <m43cap@yandex.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: , emacs-devel@gnu.org
Subject: Re: mouse not working in 'info'
Date: Sun, 25 Mar 2018 19:47:05 +0100 [thread overview]
Message-ID: <87bmfcngba.fsf@yandex.com> (raw)
In-Reply-To: <83woy0f4yp.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 25 Mar 2018 20:19:26 +0300")
>>>>> Eli Zaretskii <eliz@gnu.org> writes:
>> From: Colin Baxter <m43cap@yandex.com> Cc: emacs-devel@gnu.org
>> Cc: Date: Sun, 25 Mar 2018 18:03:53 +0100
>>
>> >> M-x ;; execute-extended-command i ;; self-insert-command n ;;
>> >> self-insert-command f ;; self-insert-command o ;; >>
>> self-insert-command <return> ;; minibuffer-complete-and-exit >>
>> <help-echo> <help-echo> <help-echo> <help-echo> <down-mouse-1> ;;
>> >> mouse-drag-region <help-echo> <mouse-movement> ;; >>
>> anonymous-command <mouse-1> ;; Info-mouse-follow-nearest-node >>
>> <help-echo> <help-echo> <help-echo> <down-mouse-1> ;; >>
>> mouse-drag-header-line <mouse-1> ;; nil C-h l ;; view-lossage
>>
>> > So where did those mouse-2 and mouse-3 come from? "C-h l" says
>> > that Emacs only saw mouse-1 buttons. Do you have some >
>> button-rebinding customizations?
>>
>> Not that I'm aware off. There's no issue using emacs-26-0.91
>> (pretest) or emacs-25.3.1 (all with emacs -q).
> Ah, now that you say this is only on the trunk, I see it on my
> system as well. I was duped by your reference to a 2-button
> mouse, which evidently has nothing to do with this problem.
> Could you see if commit 3d5e31e is somehow involved in this?
I've revert commit 3d5e31eceb9dc1fb62b2b27bcab549df3bd04ce9 and the
mouse problem does indeed go away. I can now navigate up the info nodes
successfully.
prev parent reply other threads:[~2018-03-25 18:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-25 14:15 mouse not working in 'info' Colin Baxter
2018-03-25 15:28 ` Eli Zaretskii
2018-03-25 15:47 ` Colin Baxter
2018-03-25 16:44 ` Eli Zaretskii
2018-03-25 17:03 ` Colin Baxter
2018-03-25 17:19 ` Eli Zaretskii
2018-03-25 17:32 ` Eli Zaretskii
2018-03-25 20:10 ` Stefan Monnier
2018-03-26 15:00 ` Eli Zaretskii
2018-03-25 18:47 ` Colin Baxter [this message]
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=87bmfcngba.fsf@yandex.com \
--to=m43cap@yandex.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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).