From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 5557@debbugs.gnu.org, lennart.borgman@gmail.com
Subject: bug#5557: <left-margin> <double-wheel-down> is undefined
Date: Tue, 01 Oct 2019 19:36:59 +0300 [thread overview]
Message-ID: <834l0sa0d0.fsf@gnu.org> (raw)
In-Reply-To: <87o8z0zasn.fsf@gnus.org> (message from Lars Ingebrigtsen on Tue, 01 Oct 2019 18:32:24 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: lennart.borgman@gmail.com, 5557@debbugs.gnu.org
> Date: Tue, 01 Oct 2019 18:32:24 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > I actually am not sure a click on the margins should produce the same
> > effect as on the text area. The margins are used to display different
> > text from what's in the text area, so I'm not sure I understand the
> > rationale.
>
> Oh, I assumed that this was about scrolling, but that's probably not
> what <double-wheel-down> does?
Sorry for confusing wording: it _is_ about scrolling.
double-wheel-down means turning the wheel more than one click down.
What holds me back is that no other area of the display reacts to
mouse-wheel as the text area. E.g., turning the wheel on the fringes
or on the scroll bar produces the same "undefined" message as for
margins.
I'm guessing that the OP wanted to have the display scrolled no matter
where on display the user turns the mouse wheel, but evidently that's
not how things are defined by default. If we decide to change that,
it IMO makes little sense to do that only for the margins, but not for
the fringes or the scroll bar.
next prev parent reply other threads:[~2019-10-01 16:36 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 [this message]
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
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=834l0sa0d0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=5557@debbugs.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.