From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Font setting for runemacs and frame
Date: Thu, 14 Feb 2019 19:01:58 +0200 [thread overview]
Message-ID: <83k1i2nw1l.fsf@gnu.org> (raw)
In-Reply-To: <m2bm3ez8cj.fsf@gmail.com> (message from Robert Pluim on Thu, 14 Feb 2019 16:40:44 +0100)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: help-gnu-emacs@gnu.org
> Date: Thu, 14 Feb 2019 16:40:44 +0100
>
> > This is documented behavior: to modify the looks ofg the first frame,
> > you need to set initial-frame-alist in addition to
> > default-frame-alist.
>
> The docstring for 'initial-frame-alist' says:
>
> Parameters specified here supersede the values given in
> `default-frame-alist'.
>
> which certainly reads to me like 'configure only default-frame-alist
> if you want all frames including the initial one to be identical'.
Oops, I stand corrected. I guess the problem was that the alist was
set in a hook rather than directly.
next prev parent reply other threads:[~2019-02-14 17:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 10:03 Font setting for runemacs and frame Shuguang Sun
2019-02-12 16:17 ` Eli Zaretskii
2019-02-13 3:27 ` Shuguang Sun
[not found] ` <vk5yimxo9xlw.fsf@qq.com>
2019-02-13 3:40 ` Eli Zaretskii
2019-02-13 5:08 ` Shuguang Sun
[not found] ` <vk5ybm3g2s3t.fsf@qq.com>
2019-02-14 15:04 ` Eli Zaretskii
2019-02-14 15:28 ` Shuguang Sun
2019-02-14 15:40 ` Robert Pluim
2019-02-14 17:01 ` Eli Zaretskii [this message]
2019-02-14 17:14 ` Robert Pluim
2019-02-15 9:57 ` Robert Pluim
2019-02-15 10:01 ` Shuguang Sun
2019-02-16 3:11 ` next new frame's height after initial frame (Was: Font setting for runemacs and frame) Van L
[not found] ` <vk5yimxl1ibv.fsf@qq.com>
2019-02-15 14:24 ` Font setting for runemacs and frame Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2019-02-12 10:03 Shuguang Sun
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=83k1i2nw1l.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).