From: Drew Adams <drew.adams@oracle.com>
To: Christopher Dimech <dimech@gmx.com>
Cc: Help Gnu Emacs <help-gnu-emacs@gnu.org>
Subject: RE: RE: RE: RE: Viewing Info Files - Introduce Top Menu also before end of buffer
Date: Sat, 17 Oct 2020 09:37:48 -0700 (PDT) [thread overview]
Message-ID: <7fb3de73-3a59-4769-8dd1-3a3b27728237@default> (raw)
In-Reply-To: <trinity-460cc2af-e5f1-4d23-a683-e832e3cb48bb-1602892303419@3c-app-mailcom-bs14>
> Have tried your suggestion and ended up commenting everything and
> loading just your code. Scroll up gets me to the First Node I visited,
> Scroll Down gets me to Last Node I visited.
Aha. Sorry for the trouble, and thanks for your report.
Yes, Info+ made these mouse key-bindings in `Info-mode-map':
(define-key Info-mode-map [mouse-4] 'Info-history-back)
(define-key Info-mode-map [mouse-5] 'Info-history-forward)
But that's not correct for systems that use `mouse-[45]'
events for mouse-wheel scrolling instead of for buttons
4 and 5.
Please try the latest info+.el version, which removes
those two bindings for systems like yours.
___
FYI, node `Misc Events' of the Elisp manual tells us:
‘(wheel-up POSITION)’
‘(wheel-down POSITION)’
These kinds of event are generated by moving a mouse wheel....
This kind of event is generated only on some kinds of systems.
On some systems, ‘mouse-4’ and ‘mouse-5’ are used instead.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
___
On other systems, such as MS Windows, it's common for
`mouse-[45]' to be used for browser etc. history Back
and Forward. `mouse-4' and `mouse-5' (and `-6' etc.)
are legitimate mouse buttons, for mice that have more
than three buttons. But on some systems those events
are co-opted, in Emacs at least, to represent mouse
wheel movement, so they can't be used for history
navigation.
next prev parent reply other threads:[~2020-10-17 16:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 20:37 Viewing Info Files - Introduce Top Menu also before end of buffer Christopher Dimech
2020-10-16 21:11 ` Drew Adams
2020-10-16 21:18 ` Christopher Dimech
2020-10-16 21:23 ` Christopher Dimech
2020-10-16 21:46 ` Christopher Dimech
2020-10-16 21:58 ` Drew Adams
2020-10-16 22:58 ` Christopher Dimech
2020-10-16 23:08 ` Drew Adams
2020-10-16 23:51 ` Christopher Dimech
2020-10-17 16:37 ` Drew Adams [this message]
2020-10-17 18:01 ` Christopher Dimech
2020-10-17 18:05 ` RE: RE: RE: " Christopher Dimech
2020-10-17 18:39 ` Drew Adams
2020-10-17 19:03 ` Christopher Dimech
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=7fb3de73-3a59-4769-8dd1-3a3b27728237@default \
--to=drew.adams@oracle.com \
--cc=dimech@gmx.com \
--cc=help-gnu-emacs@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.
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).