GNU bug report logs - #37415
Asserting failure setting frame parameters to non-fixnum values in early-init.el

Previous Next

Full log

Message #89 received at 37415 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: martin rudalics <rudalics <at> gmx.at>
Cc: lekktu <at> gmail.com, 37415 <at> debbugs.gnu.org
Subject: Re: bug#37415: Asserting failure setting frame parameters to
 non-fixnum values in early-init.el
Date: Mon, 23 Sep 2019 19:08:28 +0300

> Cc: lekktu <at> gmail.com, 37415 <at> debbugs.gnu.org
> From: martin rudalics <rudalics <at> gmx.at>
> Date: Mon, 23 Sep 2019 09:32:00 +0200
> 
>  >>   >> I do hit it here.  Unless some sort of bug happens before.  For
>  >>   >> example, when using (left . foo).
>  >>   >
>  >>   > But not with (left . (- 0)), right?
>  >>
>  >> With (left . (+ 0)) but maybe not with emacs -Q.  In the backtrace below
>  >> note that it gets called from 'frame-notice-user-settings':
>  >
>  > I was asking about X, but the backtrace you show is from Windows.  Am
>  > I missing something?
> 
> You asked
> 
>    . how come we don't hit this assertion when the same expression is
>      in the init file, only in the early-init file?
> 
> and the dialogue continued as above.  So your question was clearly
> about Windows because X cannot "hit this assertion".

Sorry, I thought you were answering another of my questions.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.