From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 46963@debbugs.gnu.org
Subject: bug#46963: 28.0.50; Bad WM size hints in GTK-3 builds
Date: Sat, 06 Mar 2021 13:04:37 +0200 [thread overview]
Message-ID: <83h7lownju.fsf@gnu.org> (raw)
In-Reply-To: <8a75669a-fa60-ba6f-7f60-67b1ef3d8783@gmx.at> (message from martin rudalics on Sat, 6 Mar 2021 11:47:39 +0100)
> From: martin rudalics <rudalics@gmx.at>
> Date: Sat, 6 Mar 2021 11:47:39 +0100
>
> The culprit of the GTK3 behavior is Jan Djärv's fix for Bug#8919 which
> overrides X11 functions with homemade ones. Commenting out these
> functions fixes the behavior here. I'm not sure how to proceed though.
>
> Reverting Jan's change might break Emacs for KDE users again although I
> doubt it. A configure option is no option for people who do not build
> their Emacsen. So a Lisp option is probably the only way to go which
> means to copy the functions from SetNrmHint.c to emacsgtkfixed.c. Or
> maybe remove the emacsgtkfixed files altogether? Any ideas?
When Jan made that change, did GTK3 already exist? If not, then we
could avoid using that code for GTK3.
Alternatively, we could disallow making frames smaller than 4 lines,
because making our code jump through hoops for uses cases that are
supposed to be rare, to say the least, makes little sense to me.
next prev parent reply other threads:[~2021-03-06 11:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-06 10:47 bug#46963: 28.0.50; Bad WM size hints in GTK-3 builds martin rudalics
2021-03-06 11:04 ` Eli Zaretskii [this message]
2021-03-06 19:29 ` martin rudalics
2021-03-06 20:13 ` Eli Zaretskii
2021-03-08 8:25 ` martin rudalics
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=83h7lownju.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=46963@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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).