From: martin rudalics <rudalics@gmx.at>
To: Drew Adams <drew.adams@oracle.com>, 22105@debbugs.gnu.org
Subject: bug#22105: 25.1.50; REGRESSION - `modify-frame-parameters'
Date: Mon, 07 Dec 2015 11:35:14 +0100 [thread overview]
Message-ID: <566560E2.4010204@gmx.at> (raw)
In-Reply-To: <29534178-ce2c-4d5d-b663-75e1fddcb043@default>
> Here is perhaps a clue to the problem: Variable `thumfr-frame-parameters'
> has value ((menu-bar-lines . 0)). If you comment-out that line, to
> give it a value of (()), then there is no bug. You can also uncomment
> the commented-out lines, to give it a value of, say,
> ((tool-bar-lines . 0) (scroll-bar-width . 6) (scroll-bar-height . 6)),
> and then there is no bug either. It seems that it is the presence of
> the `menu-bar-lines' sexp that is problematic.
I suppose the behavior is indeed caused by adding and removing the menu
bar. At least when doing C-z repeatedly with the "(debug)" commented
out I see here both small and normal font frames continuously increase
in size.
You could try with
(setq frame-inhibit-implied-resize '(menu-bar-lines tool-bar-lines))
which inherently means to not resize the outer frame when adding or
removing the menu bar. It seems to cure the problem I described above.
martin
next prev parent reply other threads:[~2015-12-07 10:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-07 6:03 bug#22105: 25.1.50; REGRESSION - `modify-frame-parameters' Drew Adams
2015-12-07 10:35 ` martin rudalics [this message]
2015-12-07 17:00 ` Drew Adams
2015-12-08 9:17 ` martin rudalics
2015-12-08 14:07 ` martin rudalics
2015-12-12 10:44 ` martin rudalics
2015-12-12 10:59 ` Eli Zaretskii
2015-12-12 13:46 ` martin rudalics
2016-04-30 22:29 ` Lars Ingebrigtsen
2016-05-01 1:26 ` Drew Adams
2019-08-08 4:07 ` Stefan Kangas
2019-08-08 15:18 ` Drew Adams
2020-09-07 16:28 ` Lars Ingebrigtsen
2020-09-07 16:35 ` Eli Zaretskii
[not found] ` <<87sgbt5z63.fsf@gnus.org>
[not found] ` <<83y2llmtn7.fsf@gnu.org>
2020-09-07 17:11 ` Drew Adams
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=566560E2.4010204@gmx.at \
--to=rudalics@gmx.at \
--cc=22105@debbugs.gnu.org \
--cc=drew.adams@oracle.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.