From: Van L <van@scratch.space>
To: help-gnu-emacs@gnu.org
Subject: next new frame's height after initial frame (Was: Font setting for runemacs and frame)
Date: Sat, 16 Feb 2019 14:11:36 +1100 [thread overview]
Message-ID: <m2mumw2zrr.fsf_-_@scratch.space> (raw)
In-Reply-To: 27157.3423453205$1550224965@news.gmane.org
>
>>> However with the setting of window-system-default-frame-alist or
>>> default-frame-alist above, it takes no effect until I make a new frame
>>> (after-make-frame-functions).
>>
>> 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.
>>
On 26.1; NetBSD-8, a problem I have is setting the next new frame's
height to 25 after the initial frame. I get a default height of 4.
The settings I have include:
c) Default Frame Alist: (height 25)
d) Initial Frame Alist: (height 25)
e) Pop Up Frame Alist: (height 25)
f) Special Display Frame Alist: (height 14)
a) window-safe-min-height: 1
b) Window Min Height: 4
If I set either a) or b) directly I confuse the Minibuffer Frame's display.
Is the problem due to app default for X's resources?
How to make it do
the right thing?
--
© 2019 Van L
gpg using EEF2 37E9 3840 0D5D 9183 251E 9830 384E 9683 B835
"What's so strange when you know that you're a Wizard at 3?" -Joni Mitchell
next prev parent reply other threads:[~2019-02-16 3:11 UTC|newest]
Thread overview: 14+ 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
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 ` Van L [this message]
[not found] ` <vk5yimxl1ibv.fsf@qq.com>
2019-02-15 14:24 ` Eli Zaretskii
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=m2mumw2zrr.fsf_-_@scratch.space \
--to=van@scratch.space \
--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).