From: "Jan Djärv" <jan.h.d@swipnet.se>
To: martin rudalics <rudalics@gmx.at>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: [Fwd: Frame Height Different for Default Frame and Additional Frames]
Date: Thu, 11 Oct 2007 08:15:12 +0200 [thread overview]
Message-ID: <470DBF70.9000700@swipnet.se> (raw)
In-Reply-To: <470D38E9.1040802@gmx.at>
martin rudalics skrev:
> > I think the bug is because frame parameters for the first frame is
> > applied after the frame already has been created, but for frames created
> > later, they are applied before the frame gets created.
>
> IIUC the value of `tool-bar-mode' is known only after the first frame
> has been created. Hence we can either remove the adjustment code for the
> native tool-bar or add an entry to PROBLEMS. Is there a third way?
>
>
The obvious (but more difficult) would be to read all startup lisp before
creating the first frame. Or create an initial frame (like a splash screen),
and then replace it with a proper "editing" frame.
What I had in mind was a modeless frame with the Gnu logo and one line of text
from *Messages* at the borrom. When startup is complete, then create a proper
frame with tool bars, menus and such. Of course there are special cases to
handle, like debug on startup, errors in ~/.emacs and such.
Another way is to forcibly resize the frame after all startup code has been
read and the value of `tool-bar-mode' is known. I think Emacs used to do that
before. But it looks ugly.
Jan D.
next prev parent reply other threads:[~2007-10-11 6:15 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <002501c8044b$fcc95390$6100000a@intermedinc.internal>
[not found] ` <4701F8AC.6070900@gmx.at>
[not found] ` <E1Iewxc-0004U8-CC@fencepost.gnu.org>
2007-10-08 21:12 ` [Fwd: Frame Height Different for Default Frame and Additional Frames] martin rudalics
2007-10-09 20:02 ` Richard Stallman
2007-10-09 21:25 ` martin rudalics
2007-10-10 5:55 ` Jan Djärv
2007-10-10 6:51 ` martin rudalics
2007-10-10 7:39 ` Jan Djärv
2007-10-10 7:50 ` Jason Rumney
2007-10-10 20:41 ` martin rudalics
2007-10-11 6:15 ` Jan Djärv [this message]
2007-10-11 8:52 ` martin rudalics
2007-10-11 14:01 ` Stefan Monnier
2007-10-14 16:29 ` Richard Stallman
2007-10-11 5:19 ` Richard Stallman
2007-10-11 8:52 ` martin rudalics
2007-10-11 18:03 ` Jan Djärv
2007-12-25 17:17 ` Richard Stallman
2007-12-27 19:10 ` martin rudalics
2007-12-28 13:56 ` Richard Stallman
2007-12-28 20:06 ` martin rudalics
2007-12-28 23:09 ` Robert J. Chassell
2007-12-28 23:51 ` martin rudalics
2008-01-05 11:22 ` Jan Djärv
2008-01-05 13:08 ` martin rudalics
2008-01-05 17:33 ` Jan Djärv
2008-01-05 18:08 ` Drew Adams
2008-01-05 22:42 ` Robert J. Chassell
2008-01-05 23:00 ` Jan Djärv
2008-01-06 8:08 ` Richard Stallman
2008-01-06 20:19 ` Stefan Monnier
2008-01-06 20:45 ` [Fwd: Frame Height Different for Default Frame and AdditionalFrames] Drew Adams
2007-10-10 21:03 ` [Fwd: Frame Height Different for Default Frame and Additional Frames] Richard Stallman
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=470DBF70.9000700@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=emacs-devel@gnu.org \
--cc=rms@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 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).