From: Tak Kunihiro <tkk@misasa.okayama-u.ac.jp>
To: eliz@gnu.org
Cc: alan@idiocy.org, rpluim@gmail.com, npostavs@gmail.com,
35389@debbugs.gnu.org, homeros.misasa@gmail.com,
tkk@misasa.okayama-u.ac.jp
Subject: bug#35389: 27.0.50; [PATCH] Emacs on macOS sets mouse-wheel variables directly
Date: Thu, 06 Jun 2019 11:21:38 +0900 (JST) [thread overview]
Message-ID: <20190606.112138.417113641534588390.tkk@misasa.okayama-u.ac.jp> (raw)
In-Reply-To: <83h89n80un.fsf@gnu.org>
>> To be consistent among platform, should mouse-wheel-progressive-speed be
>> t?
>
> It'd be preferable, but I understand this makes Emacs on macOS
> unusable with mouse scrolling, so I guess we will have to turn it off
> by default on macOS.
Following patch will make mouse-wheel-scroll-amount consistent among
platform. Can you install it?
* Commit log
Author: Tak Kunihiro <tkk@misasa.okayama-u.ac.jp>
Make mouse-wheel-scroll-amount consistent among platform
* lisp/term/ns-win.el
Do not put any values on mouse-wheel-scroll-amount on ns.
* Patch
diff --git a/lisp/term/ns-win.el b/lisp/term/ns-win.el
index 6a668b213d..15f3f76838 100644
--- a/lisp/term/ns-win.el
+++ b/lisp/term/ns-win.el
@@ -745,7 +745,6 @@ mouse-wheel-progressive-speed
(string-to-number (match-string 1 ns-version-string)))))
;; Appkit 1138 ~= macOS 10.7.
(when (>= appkit-version 1138)
- (setq mouse-wheel-scroll-amount '(1 ((shift) . 5) ((control))))
(put 'mouse-wheel-scroll-amount 'customized-value
(list (custom-quote (symbol-value 'mouse-wheel-scroll-amount))))
next prev parent reply other threads:[~2019-06-06 2:21 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 9:47 bug#35389: 27.0.50; [PATCH] Emacs on macOS sets mouse-wheel variables directly Robert Pluim
2019-04-23 11:17 ` Noam Postavsky
2019-04-23 11:38 ` Robert Pluim
2019-05-10 15:29 ` Robert Pluim
2019-05-10 19:53 ` Eli Zaretskii
2019-05-10 21:25 ` Alan Third
2019-05-11 6:12 ` Eli Zaretskii
2019-05-11 9:54 ` Robert Pluim
2019-05-11 10:58 ` Eli Zaretskii
2019-05-11 22:50 ` Alan Third
2019-05-12 4:58 ` Eli Zaretskii
2019-05-12 11:05 ` Alan Third
2019-05-12 14:36 ` Eli Zaretskii
2019-05-19 12:41 ` Alan Third
2019-05-12 23:29 ` Tak Kunihiro
2019-05-13 14:26 ` Eli Zaretskii
2019-05-16 9:00 ` Tak Kunihiro
2019-05-16 13:55 ` Eli Zaretskii
2019-05-16 23:24 ` Tak Kunihiro
2019-05-17 5:39 ` Eli Zaretskii
2019-05-18 8:50 ` Tak Kunihiro
2019-05-18 9:16 ` Eli Zaretskii
2019-05-19 12:32 ` Alan Third
2019-05-22 6:22 ` Eli Zaretskii
2019-05-23 4:24 ` Tak Kunihiro
2019-05-23 4:55 ` Eli Zaretskii
2019-06-06 2:21 ` Tak Kunihiro [this message]
2019-06-07 18:31 ` Alan Third
2020-08-10 11:32 ` Lars Ingebrigtsen
2020-08-10 13:04 ` Robert Pluim
2020-08-10 13:19 ` Lars Ingebrigtsen
2019-05-11 22:53 ` Alan Third
2019-05-11 23:06 ` Alan Third
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=20190606.112138.417113641534588390.tkk@misasa.okayama-u.ac.jp \
--to=tkk@misasa.okayama-u.ac.jp \
--cc=35389@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=eliz@gnu.org \
--cc=homeros.misasa@gmail.com \
--cc=npostavs@gmail.com \
--cc=rpluim@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).