From: Eli Zaretskii <eliz@gnu.org>
To: "Johann Höchtl" <johann.hoechtl@gmail.com>, "Po Lu" <luangruo@yahoo.com>
Cc: 65829@debbugs.gnu.org
Subject: bug#65829: 29.1; pgtk build invalid clickable area in window
Date: Sat, 09 Sep 2023 09:24:57 +0300 [thread overview]
Message-ID: <83tts3vp6u.fsf@gnu.org> (raw)
In-Reply-To: <CAH4isRz1HGMkh-iOukJ+K_S_HpxVHc7RNPySowd6Kiqt2g=vaw@mail.gmail.com> (message from Johann Höchtl on Fri, 8 Sep 2023 22:29:02 +0200)
[Please use Reply All to reply, to keep the bug tracker on the CC list.]
> From: Johann Höchtl <johann.hoechtl@gmail.com>
> Date: Fri, 8 Sep 2023 22:29:02 +0200
>
> The scratch buffer in its associated window ready to be edited. It is impossible to use the mouse and
> set point as the mentioned error message appears.
>
> If I enter some text, press a few times Enter and thus have some text further down the buffer, clicks
> further down the buffer (more precise: further down from the top window border) work. It seems as
> emacs thinks there is a tab-bar while there is none.
>
> This behaviour is not just with the scratch buffer but any regular file associated buffer.
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?
next prev parent reply other threads:[~2023-09-09 6:24 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83tts3vp6u.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65829@debbugs.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 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.