From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: lekktu@gmail.com, 37415@debbugs.gnu.org
Subject: bug#37415: Asserting failure setting frame parameters to non-fixnum values in early-init.el
Date: Thu, 19 Sep 2019 10:17:42 +0200 [thread overview]
Message-ID: <14d4a455-254e-fdc2-0b64-791cfb0f7724@gmx.at> (raw)
In-Reply-To: <83imppvl9r.fsf@gnu.org>
>> Wasn't setting 'default-frame-alist' (or 'initial-frame-alist') one of
>> the major motivations for adding the early-init file feature?
>
> No. the main motivation was to be able to set package.el related
> variables.
In section 49.4.6 of the Emacs manual frames "loaded before the
package system and GUI is initialized, so in it you can customize
variables that affect frame appearance as well as the package
initialization process" come first ;-)
>> IIRC it's used to suppress temporarily showing the initial frame at
>> an unwanted position or with unwanted size. So IMHO this should
>> never fail.
>
> Feel free to fix it, if it's practical. I chimed in after hearing
> nothing from you for a few days ;-)
Initially, I couldn't reproduce it (and still can't on Debian although
setting it doesn't seem to have any effect there). But even if we
cannot fix the behavior we have to avoid the crash. After all, this
is the first release processing an early init file.
martin
next prev parent reply other threads:[~2019-09-19 8:17 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-15 22:34 bug#37415: Asserting failure setting frame parameters to non-fixnum values in early-init.el Juanma Barranquero
2019-09-17 16:01 ` Eli Zaretskii
2019-09-17 17:04 ` Juanma Barranquero
2019-09-18 7:45 ` martin rudalics
2019-09-18 12:31 ` Eli Zaretskii
2019-09-19 8:17 ` martin rudalics [this message]
2019-09-19 14:13 ` Eli Zaretskii
2019-09-20 8:13 ` martin rudalics
2019-09-20 19:08 ` Eli Zaretskii
2019-09-21 8:51 ` martin rudalics
2019-09-21 9:14 ` Eli Zaretskii
2019-09-21 10:02 ` Juanma Barranquero
2019-09-21 12:27 ` Eli Zaretskii
2019-09-22 5:54 ` Juanma Barranquero
2019-09-22 8:09 ` martin rudalics
2019-09-22 16:26 ` Eli Zaretskii
2019-09-22 8:08 ` martin rudalics
2019-09-22 16:43 ` Eli Zaretskii
2019-09-22 17:54 ` martin rudalics
2019-09-22 18:19 ` Eli Zaretskii
2019-09-23 7:32 ` martin rudalics
2019-09-23 16:35 ` Eli Zaretskii
2019-09-24 6:45 ` martin rudalics
2019-09-24 7:41 ` Eli Zaretskii
2019-09-22 8:08 ` martin rudalics
2019-09-22 16:27 ` Eli Zaretskii
2019-09-22 17:53 ` martin rudalics
2019-09-22 18:16 ` Eli Zaretskii
2019-09-23 7:32 ` martin rudalics
2019-09-23 16:08 ` Eli Zaretskii
2019-09-21 4:25 ` Juanma Barranquero
2019-09-18 2:30 ` Paul Eggert
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=14d4a455-254e-fdc2-0b64-791cfb0f7724@gmx.at \
--to=rudalics@gmx.at \
--cc=37415@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=lekktu@gmail.com \
/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).