From: Eli Zaretskii <eliz@gnu.org>
To: Hiroya Ebine <hiroya.ebine1@gmail.com>
Cc: 65070@debbugs.gnu.org
Subject: bug#65070: 29.1; (Only on Windows) Both touchpad scroll gestures scroll the screen up and down.
Date: Sat, 05 Aug 2023 12:51:54 +0300 [thread overview]
Message-ID: <831qghu891.fsf@gnu.org> (raw)
In-Reply-To: <CAMutsU2q4ukcF1FY1-Fxi5ajCf7j1=nRDz+hAKLRFnost8fk-Q@mail.gmail.com> (message from Hiroya Ebine on Sat, 5 Aug 2023 00:32:00 +0900)
> From: Hiroya Ebine <hiroya.ebine1@gmail.com>
> Date: Sat, 5 Aug 2023 00:32:00 +0900
>
> 1. c-h i (open any vertically long document)
> M-> (move to the bottom of the document) 3.
> 3. perform the scroll down gesture on the touchpad.
Is step 2 necessary for reproducing the problem? That is, does the
problem only happen at the end of a buffer?
> Then you will see the screen scroll up.
> Either scroll down or scroll up, whichever you do, the screen will scroll up.
After you do the above, what does "C-h l" show?
next prev parent reply other threads:[~2023-08-05 9:51 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 15:32 bug#65070: 29.1; (Only on Windows) Both touchpad scroll gestures scroll the screen up and down Hiroya Ebine
2023-08-05 9:04 ` bug#65070: 29.1; (Only on Windows) Both touchpad scroll gestures scroll the screen up only Hiroya Ebine
2023-08-05 10:44 ` Eli Zaretskii
2023-08-05 9:51 ` Eli Zaretskii [this message]
2023-08-07 13:18 ` bug#65070: 29.1; (Only on Windows) Both touchpad scroll gestures scroll the screen up and down Hiroya Ebine
2023-08-07 14:05 ` Eli Zaretskii
2023-08-08 10:19 ` bug#65070: max
2023-08-08 12:46 ` bug#65070: Eli Zaretskii
2023-08-08 12:54 ` bug#65070: Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-08 13:04 ` bug#65070: Eli Zaretskii
2023-08-18 16:49 ` bug#65070: 29.1; (Only on Windows) Both touchpad scroll gestures scroll the screen up and down Kazuhiro Ito
2023-08-18 18:26 ` Eli Zaretskii
2023-08-18 18:39 ` Corwin Brust
2023-08-18 22:58 ` Kazuhiro Ito
2023-08-19 7:56 ` Eli Zaretskii
2023-08-19 13:46 ` Kazuhiro Ito
2023-08-19 14:00 ` Eli Zaretskii
2023-08-18 22:54 ` Kazuhiro Ito
2023-08-19 7:54 ` Eli Zaretskii
2023-08-19 13:45 ` Kazuhiro Ito
2023-08-19 13:58 ` Eli Zaretskii
2023-08-19 15:27 ` Kazuhiro Ito
2023-08-19 15:32 ` Eli Zaretskii
2023-08-20 0:16 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-20 6:28 ` Eli Zaretskii
2023-08-20 13:14 ` Kazuhiro Ito
2023-08-20 13:34 ` Eli Zaretskii
2023-08-19 14:06 ` Eli Zaretskii
2023-08-20 0:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-20 6:34 ` Eli Zaretskii
2023-08-20 7:04 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-20 7:13 ` Eli Zaretskii
2023-08-20 7:43 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-20 8:10 ` Eli Zaretskii
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=831qghu891.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65070@debbugs.gnu.org \
--cc=hiroya.ebine1@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.