unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 57476@debbugs.gnu.org
Subject: bug#57476: 29.0.50; Mouse wheel event ignored on Lucid build
Date: Tue, 30 Aug 2022 09:25:45 +0800	[thread overview]
Message-ID: <87tu5uplnq.fsf@yahoo.com> (raw)
In-Reply-To: <8735dfe08x.fsf@rub.de> (Stephen Berman's message of "Mon, 29 Aug 2022 13:51:26 +0200")

Stephen Berman <stephen.berman@gmx.net> writes:

> 0. emacs -Q
> 1. Display a buffer with enough lines to scroll, e.g.:
>    C-x d /path/to/emacs/sources RET
> 2. Scroll mouse wheel
> => The buffers fails to scroll.
> 3. Type `C-h k' and then scroll the mouse wheel
> => The echo area shows no input, only the prompt "Describe the following
>    key, mouse click, or menu item: "
>
> I see this only on the Lucid build.  Also on Lucis, if I hold down
> mouse-1 or mouse-3 and simultaneously scroll the wheel, then the buffer
> does scroll.  After releasing mouse-1 or mouse-3, scrolling the wheel
> scrolls the buffer once by one line (either up or down).  Further
> scrolling of the wheel fails to scroll the buffer.

To be clear here, you are talking about wheel-up and wheel-down events,
correct?

Input extension builds do not normally report mouse-1 or mouse-3; that
only happens if the input extension could not be set up for some reason.





  reply	other threads:[~2022-08-30  1:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-29 11:51 bug#57476: 29.0.50; Mouse wheel event ignored on Lucid build Stephen Berman
2022-08-30  1:25 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-08-30  1:29   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-30  8:20   ` Stephen Berman
2022-08-30 10:15     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-30 10:41       ` Stephen Berman
2022-08-30 12:48         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-30 12:58           ` Stephen Berman
2022-08-30 13:44             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-30 15:15               ` Stephen Berman
2022-08-31  2:19                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-31 18:17                   ` Stephen Berman
2022-09-01 13:21                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-01 22:41                       ` Stephen Berman
2022-09-02  1:08                         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-03 11:25                           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=87tu5uplnq.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=57476@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=stephen.berman@gmx.net \
    /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).