unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Daniel Colascione <dancol@dancol.org>
Cc: emacs-devel@gnu.org
Subject: Re: Yes, please allow pre-configuration of first frame [was: Blink Cursor mode is off by default]
Date: Sat, 16 Jun 2018 13:20:21 -0400	[thread overview]
Message-ID: <jwvwouyirbd.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <5cc07aef-9c8b-4a5b-8cdb-3d003bed7151@dancol.org> (Daniel Colascione's message of "Sat, 16 Jun 2018 07:37:07 -0700")

>>> It doesn't sound right, though, that a fix for this should
>>> involve the user having to mess around with intiialisation
>>> order etc. -- it should "just work".
>>>
>>> It seems that this might be a worthwhile project for "someone"
>>> to work on? (Perhaps they could fix the problem of not being
>>> able to un-apply themes at the same time?)
>>
>> I don't really understand what you suggest doing: the .emacs file is
>> read *after* creating the first frame, so there's no way to avoid
>> "flashing" without breaking some .emacs files.
>
> The file could just run against a dummy frame that happens to look like the
> GUI frame we'll eventually create.

To reduce the breakage, the frame had batter be as real as possible
(e.g. plain normal frame, just `invisible`), but still: what will happen
when the .emacs code ends up prompting the user in the minibuffer?

It will inevitably introduce changes which in some cases are undesirable,


        Stefan



  reply	other threads:[~2018-06-16 17:20 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-11 16:48 Blink Cursor mode is off by default Eli Zaretskii
2018-06-11 17:14 ` Stefan Monnier
2018-06-11 17:32   ` Eli Zaretskii
2018-06-11 22:13     ` Stefan Monnier
2018-06-11 23:19       ` dancol
2018-06-12  2:31         ` Eli Zaretskii
2018-06-12  2:33           ` Daniel Colascione
2018-06-12  4:02             ` Eli Zaretskii
2018-06-12  4:12               ` dancol
2018-06-12 15:20                 ` Eli Zaretskii
2018-06-12 15:52                   ` Stefan Monnier
2018-06-12 16:40                     ` Eli Zaretskii
2018-06-12 16:51                       ` dancol
2018-06-15 14:14                 ` Yes, please allow pre-configuration of first frame [was: Blink Cursor mode is off by default] N. Jackson
2018-06-15 14:31                   ` Eli Zaretskii
2018-06-15 21:34                   ` Stefan Monnier
2018-06-16 14:37                     ` Daniel Colascione
2018-06-16 17:20                       ` Stefan Monnier [this message]
2018-06-16 17:26                         ` Eli Zaretskii
2018-06-16 17:33                           ` Daniel Colascione
2018-06-12 15:24               ` Blink Cursor mode is off by default Stefan Monnier
2018-06-12  2:29       ` Eli Zaretskii
2018-06-11 20:43 ` Michael Heerdegen
2018-06-12  2:26   ` 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=jwvwouyirbd.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=dancol@dancol.org \
    --cc=emacs-devel@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.
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).