unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Tak Kunihiro <tkk@misasa.okayama-u.ac.jp>, 26599@debbugs.gnu.org
Subject: bug#26599: patch for mwheel.el
Date: Mon, 24 Jun 2019 18:38:28 +0200	[thread overview]
Message-ID: <m35zovrla3.fsf@gnus.org> (raw)
In-Reply-To: <83zie92pko.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 19 May 2017 11:55:35 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> Date: Fri, 28 Apr 2017 18:12:50 +0900 (JST)
>> Cc: 26599@debbugs.gnu.org, tkk@misasa.okayama-u.ac.jp
>> From: Tak Kunihiro <tkk@misasa.okayama-u.ac.jp>
>> 
>> > What makes this special is that you want Emacs to work differently
>> > depending on the input device.  Emacs normally makes a significant
>> > effort in the other direction: to produce the same behavior no matter
>> > where input came from.
>> > 
>> > I'm not sure we want to have such unusual behavior as part of Emacs.
>> 
>> Can you take a look minor-mode that I want to invoke by hook?  I still
>> think this is potentially useful to mouse-loving cloud using
>> <wheel-left> and <wheel-right>.
>
> I'm okay with adding this to ELPA.

But for this minor mode to work, I think mwheel-pre-scroll-hook had to
be implemented, if I understood correctly?

This is two years old, though, so I'm not sure any of this is still an
issue...

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2019-06-24 16:38 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-22  1:27 bug#26599: patch for mwheel.el Tak Kunihiro
2017-04-22  7:52 ` Eli Zaretskii
2017-04-23  6:13   ` Tak Kunihiro
2017-04-26  5:01     ` Eli Zaretskii
2017-04-26  6:08       ` Tak Kunihiro
2017-04-26 10:50         ` Eli Zaretskii
2017-04-26 12:32           ` Tak Kunihiro
2017-04-26 15:31             ` Eli Zaretskii
2017-04-26 23:33               ` Tak Kunihiro
2017-04-27  2:36                 ` Eli Zaretskii
2017-04-27  5:27                   ` Tak Kunihiro
2017-04-27 14:25                     ` Eli Zaretskii
2017-04-27 23:16                       ` Tak Kunihiro
2017-04-28  6:47                         ` Eli Zaretskii
2017-04-28  9:12                           ` Tak Kunihiro
2017-05-19  8:55                             ` Eli Zaretskii
2019-06-24 16:38                               ` Lars Ingebrigtsen [this message]
2020-01-20 20:06                                 ` Stefan Kangas
2020-01-20 22:47                                   ` Juri Linkov
2020-01-21  7:17                                     ` Tak Kunihiro
2020-01-21  9:46                                       ` Stefan Kangas
2020-01-22  5:46                                         ` Tak Kunihiro
2020-03-13 23:43                                           ` Tak Kunihiro
2020-03-13 23:52                                         ` Tak Kunihiro

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=m35zovrla3.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=26599@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=tkk@misasa.okayama-u.ac.jp \
    /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).