From: "Jan Djärv" <jan.h.d@swipnet.se>
To: jidanni@jidanni.org, 4995@emacsbugs.donarmstrong.com
Cc: emacs-pretest-bug@gnu.org, rfrancoise@debian.org
Subject: bug#4995: 23.1.50; No size compensation for (tool-bar-mode 0)(menu-bar-mode 0)
Date: Sat, 21 Nov 2009 00:09:01 +0100 [thread overview]
Message-ID: <4B07218D.8030206@swipnet.se> (raw)
In-Reply-To: <87bpix0xus.fsf@jidanni.org>
jidanni@jidanni.org skrev 2009-11-20 21.01:
> ADMIT that
> $ emacs -Q -eval '(progn(tool-bar-mode 0)(menu-bar-mode 0))'
> 1. Still momentarily wastefully shows at least the menu-bar before cleaning it
> off the screen, even if the user does those commands in his .emacs file.
That is because the first frame is visible before .emacs is read, an issue
discussed before.
> 2. But more importantly, gives the user a window shorter than he wants.
> No compensation is made here under X windows to lengthen back the emacs
> window back to the size it was before removing those items.
There are three ways of doing this:
1 Keep number of editable lines
2 Keep height in pixels.
3 Read .emacs before the first frame.
IMHO, the last is the correct solution, but it isn't such a high priority.
After all this is kostly a cosmetic bug, even if annoying.
1 or 2 is equally correct in my eye, if 3 isn't present.
> (Note I had no xrdb emacs items set.) To workaround I must do:
> (setq default-frame-alist (cons (cons 'height (+(frame-height)4)) default-frame-alist))
> (No, fullhight, fullboth,(which by the way is not documented) don't let
> one still see the ICEWM toolbar.)
Currently Emacs just tells the WM to do the resizing, so if some WM-specific
toolbar isn't shown, Emacs is not to blame.
You are just not looking hard enough for documentation:
% emacs -Q
C-h i
m elisp<return>
s fullscreen<return>
Jan D.
prev parent reply other threads:[~2009-11-20 23:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 20:01 bug#4995: 23.1.50; No size compensation for (tool-bar-mode 0)(menu-bar-mode 0) jidanni
2009-11-20 23:09 ` Jan Djärv [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B07218D.8030206@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=4995@emacsbugs.donarmstrong.com \
--cc=emacs-pretest-bug@gnu.org \
--cc=jidanni@jidanni.org \
--cc=rfrancoise@debian.org \
/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.