all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ynyaaa@gmail.com
To: martin rudalics <rudalics@gmx.at>
Cc: 38684@debbugs.gnu.org
Subject: bug#38684: 26.3; toggle menu bar twice may change frame height
Date: Sun, 22 Dec 2019 21:28:18 +0900	[thread overview]
Message-ID: <865zi8r1ct.fsf@gmail.com> (raw)
In-Reply-To: <ec7e31b9-7890-d446-d59c-dd63ecc25eae@gmx.at> (martin rudalics's message of "Fri, 20 Dec 2019 19:29:55 +0100")

martin rudalics <rudalics@gmx.at> writes:

>> If the frame is narrow enough to display the menu bar for current buffer
>> in two lines and wide enough to display the menu bar for minibuffer in
>> one line, toggling menu bar using minibuffer(M-x menu-bar-mode) twice
>> enlarges the frame height.
>>
>>
>> In GNU Emacs 26.3 (build 1, x86_64-w64-mingw32)
>>   of 2019-08-29 built on CIRROCUMULUS
>> Repository revision: 96dd0196c28bc36779584e47fffcca433c9309cd
>> Windowing system distributor 'Microsoft Corp.', version 6.3.9600
>> Recent messages:
>
> Adding 'menu-bar-lines' to 'frame-inhibit-implied-resize' should be
> the second best cure for that (setting 'frame-inhibit-implied-resize'
> to t being certainly the best).  Other than that, I strongly doubt
> that anyone will fix such corner cases.  Or maybe you want to give it
> a try?
>
> martin

I didn't know the variable. Thank you.

Descriptions in info (elisp)Implied Frame Resizing and
in help C-h v frame-inhibit-implied-resize slightly differ.

first paragraph
info: If this option is non-‘nil’, no implied resizing is done.
help: If this option is t, no such resizing is done.

second paragraph
info: The value of this option can be also a list
help: The value of this option can be also be a list





  reply	other threads:[~2019-12-22 12:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-20  2:44 bug#38684: 26.3; toggle menu bar twice may change frame height ynyaaa
2019-12-20 18:29 ` martin rudalics
2019-12-22 12:28   ` ynyaaa [this message]
2019-12-23 10:07     ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=865zi8r1ct.fsf@gmail.com \
    --to=ynyaaa@gmail.com \
    --cc=38684@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 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.