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: Fri, 14 Aug 2020 14:34:25 -0700 [thread overview]
Message-ID: <CADwFkm=AO7tZUhP+kM2=1TzR-aja6ZRM=hV75wzk+XE5TNVZXw@mail.gmail.com> (raw)
In-Reply-To: <835z9lkpm8.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> I just don't want us to usurp key bindings without a good reason.
I tried arguing that being more like other applications here makes for a
better user experience. To me that's a good reason.
Plus I really don't know why someone would want to do anything but
scroll using the mouse wheel, or why users (or package authors) can't
rebind this on specific window areas should they want to.
> Let's leave the unbound mouse gestures unbound, and leave it to the
> users to decide what effect they have on different parts of the
> display. There's no reason to force them all to do the same on any
> part of the display, when we don't even know what commands will be
> bound to them.
OK, I guess we will have to agree to disagree.
One thing I don't understand is how binding to scroll-bar is supposed to
work. I tried the following, but it didn't work (tested in GTK and
lucid):
(global-set-key [vertical-scroll-bar mouse-5] 'foo-mouse-message)
(defun foo-mouse-message (event)
(interactive "e")
(message "%s" (format-time-string "%H:%M:%S")))
(Change vertical-scroll-bar to left-fringe to see that it works there.)
Any ideas?
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2020-08-14 21:34 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 [this message]
2020-08-15 17:40 ` Eli Zaretskii
2020-08-16 13:41 ` Stefan Kangas
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADwFkm=AO7tZUhP+kM2=1TzR-aja6ZRM=hV75wzk+XE5TNVZXw@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 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.