From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 5557@debbugs.gnu.org, larsi@gnus.org, lennart.borgman@gmail.com
Subject: bug#5557: <left-margin> <double-wheel-down> is undefined
Date: Sun, 16 Aug 2020 06:41:32 -0700 [thread overview]
Message-ID: <CADwFkmk9ofHaOgDR7Xy=0rMYKuv_VSuBcQSibr1uyNqWjv_qSQ@mail.gmail.com> (raw)
In-Reply-To: <835z9jkdu6.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> First, you don't need to do anything for vertical-scroll-bar, as the
> mouse wheel is already handled there, at least on my system.
Not here, unfortunately. Tried emacs -Q with both GTK and Lucid: no
message from foo-mouse-message.
On GTK, I see this:
"[The] 'bar' (inside the scroll bar) that indicates the current
position strangely moves downwards slowly. I get no error message,
and the window doesn't scroll."
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=5557#28
On Lucid, nothing at all happens for the mouse wheel. (Which is
actually better than the odd behaviour I see on GTK.)
> On a horizontal scroll-bar, if I use this:
>
> (global-set-key [horizontal-scroll-bar wheel-up] 'foo-mouse-message)
>
> I get the expected result on my system.
>
> What do you see Emacs say if you turn the wheel on the horizontal
> scroll-bar in "emacs -Q"?
Same here: no message with the binding. Instead:
On GTK, the horizontal scroll bar moves, but the window doesn't update.
The behaviour is similar to the vertical case: the 'bar' portion moves,
and when I then drag it with mouse-1, the window jumps to the position.
On Lucid, I see the same as for the vertical scroll bar: nothing happens.
So it's starting to sound like we have at least two separate bugs to
handle.
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2020-08-16 13:41 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 13:01 bug#5557: <left-margin> <double-wheel-down> is undefined Lennart Borgman
2019-10-01 15:36 ` Lars Ingebrigtsen
2019-10-01 16:09 ` Eli Zaretskii
2019-10-01 16:19 ` Lars Ingebrigtsen
2019-10-01 16:26 ` Eli Zaretskii
2019-10-01 16:32 ` Lars Ingebrigtsen
2019-10-01 16:36 ` Eli Zaretskii
2019-10-01 17:39 ` Stefan Kangas
2019-10-01 18:31 ` Eli Zaretskii
2019-10-01 18:43 ` Stefan Kangas
2019-10-01 19:06 ` Eli Zaretskii
2019-10-02 8:55 ` martin rudalics
2019-10-03 15:35 ` Lars Ingebrigtsen
2019-10-03 18:11 ` martin rudalics
2020-08-13 5:34 ` Stefan Kangas
2020-08-13 8:42 ` Lars Ingebrigtsen
2020-08-13 13:06 ` Eli Zaretskii
2020-08-14 18:38 ` Stefan Kangas
2020-08-14 19:13 ` Eli Zaretskii
2020-08-14 21:34 ` Stefan Kangas
2020-08-15 17:40 ` Eli Zaretskii
2020-08-16 13:41 ` Stefan Kangas [this message]
2020-08-16 14:48 ` Eli Zaretskii
2020-08-16 15:57 ` Stefan Kangas
2020-08-17 13:30 ` Stefan Kangas
2020-08-22 7:32 ` Eli Zaretskii
2020-08-22 11:48 ` Stefan Kangas
2020-08-22 11:59 ` Eli Zaretskii
2020-08-22 12:11 ` Stefan Kangas
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='CADwFkmk9ofHaOgDR7Xy=0rMYKuv_VSuBcQSibr1uyNqWjv_qSQ@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=5557@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=lennart.borgman@gmail.com \
/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).