From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: luangruo@yahoo.com, 53232@debbugs.gnu.org, john@yates-sheets.org
Subject: bug#53232: reopen 53232
Date: Mon, 17 Jan 2022 19:37:31 +0200 [thread overview]
Message-ID: <8335lmw9es.fsf@gnu.org> (raw)
In-Reply-To: <87ilui5l7h.fsf@gnus.org> (message from Lars Ingebrigtsen on Mon, 17 Jan 2022 18:24:50 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Mon, 17 Jan 2022 18:24:50 +0100
> Cc: Po Lu <luangruo@yahoo.com>, 53232@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?
next prev parent reply other threads:[~2022-01-17 17:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 16:50 bug#53232: 29.0.50; pgtk startup: flashes white background before painting black John Yates
2022-01-14 7:52 ` Lars Ingebrigtsen
2022-01-14 11:50 ` Eli Zaretskii
2022-01-15 7:59 ` Lars Ingebrigtsen
2022-01-15 21:46 ` bug#53232: reopen 53232 John Yates
2022-01-17 17:24 ` Lars Ingebrigtsen
2022-01-17 17:37 ` Eli Zaretskii [this message]
2022-01-17 20:39 ` bug#53232: close 53232 John Yates
2022-01-18 2:12 ` John Yates
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=8335lmw9es.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=53232@debbugs.gnu.org \
--cc=john@yates-sheets.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.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).