unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: PierGianLuca <luca@magnaspesmeretrix.org>
To: help-gnu-emacs@gnu.org
Cc: Po Lu <luangruo@yahoo.com>
Subject: Re: 4 pixels missing at startup (was: menu-bar-mode makes frame continuously shrink in height)
Date: Thu, 19 Oct 2023 13:41:51 +0200	[thread overview]
Message-ID: <a3f70715-7ce5-1b0a-3485-73a21d994511@magnaspesmeretrix.org> (raw)
In-Reply-To: <87jzri6gw3.fsf@yahoo.com>

Hi Po, thank you for the feedback. Something else interesting is coming up:

> Do frames
> continue to shrink after setting frame-resize-pixelwise to t in
> early-init.el?

Thank you, that solved the problem with menu/tool-bar!


> More likely, your window manager is imposing stringent size requirements
> pursuant to the resize increments Emacs has requested.  
I forgot to mention that I work with KDE Plasma, and I have a specific window rule for Emacs windows, to obey any geometry that they request (see details at end of email*).


While playing with geometries I've noted something else strange. I use desktop-save, so Emacs always restarts with the latest frame & geometry configuration.

However, I'm noticing now that one of the restarted frames always lacks 4 pixels in its vertical scroll bar. I've tried to specify scroll-bar-width in the init.el and early-init.el, but those four pixels disappear at every Emacs restart.

Maybe it's due to my using the lucid theme, rather than GTK...

Cheers,
Luca


* See "Ignore requested geometry" and "Obey geometry restrictions" here:

https://docs.kde.org/stable5/en/kwin/kcontrol/windowspecific/attributes.html



  reply	other threads:[~2023-10-19 11:41 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   ` PierGianLuca [this message]
2023-10-19 11:57     ` 4 pixels missing at startup Po Lu
2023-10-19 14:13       ` PierGianLuca

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=a3f70715-7ce5-1b0a-3485-73a21d994511@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).