From: PierGianLuca <luca@magnaspesmeretrix.org>
To: help-gnu-emacs@gnu.org
Cc: Po Lu <luangruo@yahoo.com>
Subject: Re: 4 pixels missing at startup
Date: Thu, 19 Oct 2023 16:13:14 +0200 [thread overview]
Message-ID: <7fdcc4b0-b94b-9f9b-b96e-d128a1e9d18b@magnaspesmeretrix.org> (raw)
In-Reply-To: <878r7y6d0h.fsf@yahoo.com>
Hi Po, thank you again for very useful feedback!
> What about under the no toolkit build? The X toolkit intrinsics seek to
> enforce client-requested size hints independently of the window manager
> under certain situations.
Had never tried that (so this is not the same as "lucid", right?), sounds interesting, I'll try it out and report back :)
Cheers,
Luca
prev parent reply other threads:[~2023-10-19 14:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 8:29 menu-bar-mode makes frame continuously shrink in height PierGianLuca
2023-10-19 10:33 ` Po Lu
2023-10-19 11:41 ` 4 pixels missing at startup (was: menu-bar-mode makes frame continuously shrink in height) PierGianLuca
2023-10-19 11:57 ` 4 pixels missing at startup Po Lu
2023-10-19 14:13 ` PierGianLuca [this message]
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=7fdcc4b0-b94b-9f9b-b96e-d128a1e9d18b@magnaspesmeretrix.org \
--to=luca@magnaspesmeretrix.org \
--cc=help-gnu-emacs@gnu.org \
--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.
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).