From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 55970@debbugs.gnu.org, lumarzeli30@gmail.com
Subject: bug#55970: 29.0.50; Emacs crashes when dragging the scroll bar with "--with-pgtk" and "--without-toolkit-scroll-bars" configure flags
Date: Wed, 15 Jun 2022 05:28:57 +0300 [thread overview]
Message-ID: <83k09islqu.fsf@gnu.org> (raw)
In-Reply-To: <87h74m91xz.fsf@yahoo.com> (message from Po Lu on Wed, 15 Jun 2022 08:59:20 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: समीर सिंह Sameer Singh
> <lumarzeli30@gmail.com>, 55970@debbugs.gnu.org
> Date: Wed, 15 Jun 2022 08:59:20 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Thanks for testing, I will let it to Po Lu to decide whether that's
> > the proper fix in this case.
>
> Non-toolkit scroll bars use different kinds of events compared to
> toolkit scroll bars. PGTK only implements the latter kind, so turning
> toolkit scroll bars off should trigger this piece of configure.ac:
>
> elif test "${window_system}" != "x11" && "${window_system}" != "none"; then
> AC_MSG_ERROR(Non-toolkit scroll bars are not implemented for your system)
> fi
>
> Perhaps Sameer's configure script is out of date and needs to be
> regenerated.
OK, but please explain how come the code in pgtk_send_scroll_bar_event
leaves the modifiers unset, and that is still OK, notwithstanding the
code in keyboard.c that expects either up or down modifier for any
mouse click event? Isn't that a bug regardless?
next prev parent reply other threads:[~2022-06-15 2:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 14:08 bug#55970: 29.0.50; Emacs crashes when dragging the scroll bar with "--with-pgtk" and "--without-toolkit-scroll-bars" configure flags समीर सिंह Sameer Singh
2022-06-14 17:44 ` Eli Zaretskii
2022-06-14 17:48 ` समीर सिंह Sameer Singh
2022-06-14 18:30 ` Eli Zaretskii
2022-06-14 18:44 ` समीर सिंह Sameer Singh
2022-06-14 18:48 ` Eli Zaretskii
2022-06-15 0:59 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-15 2:28 ` Eli Zaretskii [this message]
2022-06-15 3:29 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-15 8:23 ` समीर सिंह Sameer Singh
2022-06-15 12:25 ` Eli Zaretskii
2022-06-15 13:14 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-15 13:50 ` Robert Pluim
2022-06-15 14:01 ` समीर सिंह Sameer Singh
2022-06-16 0:53 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-16 7:39 ` Robert Pluim
2022-06-15 0:56 ` 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=83k09islqu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=55970@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=lumarzeli30@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).