From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "Johann Höchtl" <johann.hoechtl@gmail.com>
Cc: 65829@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#65829: 29.1; pgtk build invalid clickable area in window
Date: Sun, 10 Sep 2023 09:02:33 +0800 [thread overview]
Message-ID: <87jzsyc02e.fsf@yahoo.com> (raw)
In-Reply-To: <ac6278793c5ca8f11273ed63c03ebe694bae603e.camel@gmail.com> ("Johann Höchtl"'s message of "Sat, 09 Sep 2023 20:07:12 +0200")
Johann Höchtl <johann.hoechtl@gmail.com> writes:
> On Sat, 2023-09-09 at 14:35 +0800, Po Lu wrote:
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> > You are basically saying that, wherever you click mouse-1, Emacs in
>> > your PGTK build thinks the click was on the tool bar?
>> >
>> > Po Lu, do we know about such problems in the PGTK build?
>>
>> No, we don't. Johann, have you enabled tool-bar-mode or tab-bar-
>> mode?
>> Which pertinent variables have you customized?
>
> While I am aware of tool-bar-mode or tab-bar-mode, the behaviour shows
> when starting as emacs -Q, so it shows without any configuration
> walking astray from the defaults.
Thanks. What if you delete the body of the function
`pgtk_toolkit_position' within pgtkterm.c?
next prev parent reply other threads:[~2023-09-10 1:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 18:48 bug#65829: 29.1; pgtk build invalid clickable area in window Johann Höchtl
2023-09-08 18:59 ` Eli Zaretskii
[not found] ` <CAH4isRz1HGMkh-iOukJ+K_S_HpxVHc7RNPySowd6Kiqt2g=vaw@mail.gmail.com>
2023-09-09 6:24 ` Eli Zaretskii
2023-09-09 6:35 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-09 18:07 ` Johann Höchtl
2023-09-10 1:02 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-09-10 16:55 ` Johann Höchtl
2023-09-10 17:03 ` Eli Zaretskii
2023-10-23 20:04 ` Stefan Kangas
2023-10-24 8:29 ` Johann Höchtl
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=87jzsyc02e.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=65829@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=johann.hoechtl@gmail.com \
--cc=luangruo@yahoo.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).