GNU bug report logs - #53232
29.0.50; pgtk startup: flashes white background before painting black

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: luangruo <at> yahoo.com, 53232 <at> debbugs.gnu.org, john <at> yates-sheets.org
Subject: bug#53232: reopen 53232
Date: Mon, 17 Jan 2022 19:37:31 +0200

> From: Lars Ingebrigtsen <larsi <at> gnus.org>
> Date: Mon, 17 Jan 2022 18:24:50 +0100
> Cc: Po Lu <luangruo <at> yahoo.com>, 53232 <at> debbugs.gnu.org
> 
> > That said, the sub-optimal behavior is real:
> >
> > * early-init.el:
> >
> >     (custom-set-variables
> >      '(default-frame-alist
> >        '((fullscreen . maximized)
> >          (background-color . "#000000")
> >          (foreground-color . "#ffffff")))
> >      '(inhibit-startup-screen t)
> >     )
> >
> > * init.el:
> >
> >     [EMPTY]
> 
> I'm unable to reproduce this with or without pgtk -- Emacs doesn't flash
> the default background colour on startup, as far as I can tell.  (This
> is on Debian/bookworm with Gnome Shell, if that matters.)

Isn't it true that to have the initial frame appear from the get-go
with some non-default attributes, one must change the X resources?  I
have a vague recollection that this was always like that, and was
never perceived as a problem.  How do you want Emacs to perform the
initialization without first creating a GUI frame, and how can it
create the first GUI frame except with the default attributes?

Previous Next

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