From: uzibalqa via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 57758@debbugs.gnu.org
Subject: bug#57758: Using menu-bar-mode and tool-bar-mode changes frame size
Date: Tue, 13 Sep 2022 04:05:48 +0000 [thread overview]
Message-ID: <mnJdmXV3w8-AIOXUQqt5KGNu9vtd0S6kvASlAlCza7n7KKOL5ZkGQ9UDMPFowTTvO2RmF_NeAdAwHpobSObMG-rX5k3vCauuZ3_2KvlALpw=@proton.me> (raw)
In-Reply-To: <87y1uo0vyf.fsf@yahoo.com>
------- Original Message -------
On Tuesday, September 13th, 2022 at 3:55 AM, Po Lu <luangruo@yahoo.com> wrote:
> uzibalqa uzibalqa@proton.me writes:
>
> > Why does a resize happen and why is it not a bug?
>
>
> Because changing the state of the tool bar and/or menu bar changes the
> size of the frame.
It makes more sense to change the size of the window instead of the frame.
Particularly for people having multiple screens of different sizes. The frame
resize poses the problem of having the frame get beyond the screen region,
with no way to access the menu-bar.
next prev parent reply other threads:[~2022-09-13 4:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 21:45 bug#57758: Using menu-bar-mode and tool-bar-mode changes frame size uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-13 2:28 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-13 3:20 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-13 3:52 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-13 3:55 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-13 4:05 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-09-13 4:56 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-13 11:57 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-13 13:00 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
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='mnJdmXV3w8-AIOXUQqt5KGNu9vtd0S6kvASlAlCza7n7KKOL5ZkGQ9UDMPFowTTvO2RmF_NeAdAwHpobSObMG-rX5k3vCauuZ3_2KvlALpw=@proton.me' \
--to=bug-gnu-emacs@gnu.org \
--cc=57758@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=uzibalqa@proton.me \
/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).