From: carlosjosepita@gmail.com
To: 18155@debbugs.gnu.org
Subject: bug#18155: 24.3.92; Honor toolBar resource *before* showing frame
Date: Wed, 30 Jul 2014 19:27:14 -0300 [thread overview]
Message-ID: <86mwbq4h4t.fsf@localhost.i-did-not-set--mail-host-address--so-tickle-me> (raw)
The elisp reference states that:
> Emacs creates the initial frame before it reads your init file. After
> reading that file, Emacs checks initial-frame-alist, and applies the
> parameter settings in the altered value to the already created initial
> frame.
> If these settings affect the frame geometry and appearance, you'll see
> the frame appear with the wrong ones and then change to the specified
> ones. If that bothers you, you can specify the same geometry and
> appearance with X resources; those do take effect before the frame is
> created. See X Resources.
This is true except when the toolbar is visible. In this case, no matter
the value of the toolBar resource, the frame is initially shown without
a toolbar and then the geometry is modified to fit the toolbar. This
produces unpleasant visual artifacts during emacs startup.
I'm afraid that fixing this will require to add a resource to set the
toolbar position, too. I don't know how viable this is. In case it's not
desirable to implement this feature I think some remark has to be added
to the aforementioned documentation excerpt. Otherwise this is indeed a
bug, as the behavior contradicts what's documented.
Cheers
--
Carlos
next reply other threads:[~2014-07-30 22:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 22:27 carlosjosepita [this message]
2014-07-31 4:51 ` bug#18155: 24.3.92; Honor toolBar resource *before* showing frame Eli Zaretskii
2014-07-31 5:17 ` Carlos Pita
2014-07-31 5:53 ` Eli Zaretskii
2014-07-31 6:57 ` Jan D.
2014-07-31 7:11 ` Eli Zaretskii
2014-07-31 7:17 ` Carlos Pita
2014-07-31 11:29 ` Jan Djärv
2014-07-31 12:08 ` Eli Zaretskii
2014-07-31 8:49 ` martin rudalics
2014-07-31 9:12 ` Carlos Pita
2014-07-31 11:32 ` Jan Djärv
2014-07-31 15:52 ` Stefan Monnier
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=86mwbq4h4t.fsf@localhost.i-did-not-set--mail-host-address--so-tickle-me \
--to=carlosjosepita@gmail.com \
--cc=18155@debbugs.gnu.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.