From: Eli Zaretskii <eliz@gnu.org>
To: dancol@dancol.org
Cc: monnier@IRO.UMontreal.CA, emacs-devel@gnu.org
Subject: Re: Blink Cursor mode is off by default
Date: Tue, 12 Jun 2018 05:31:35 +0300 [thread overview]
Message-ID: <83o9ggpwfs.fsf@gnu.org> (raw)
In-Reply-To: <13a2189b89d06be494cbc21561713d5d.squirrel@dancol.org>
> Date: Mon, 11 Jun 2018 16:19:42 -0700
> From: dancol@dancol.org
> Cc: "Eli Zaretskii" <eliz@gnu.org>,
> emacs-devel@gnu.org
>
> >> Well, yes, but they aren't supposed to do that in that file, right?
>
> What about temporarily setting a variable watcher on blink-cursor-mode so
> we can tell whether early init touched it?
I think it's too gross.
> > Not sure: a valid choice now is to do all your customizations in
> > early-init.el and not use any .emacs.d/init.el at all.
>
> That's what I do now.
I suggest you don't. This is not what early-init.el is for.
next prev parent reply other threads:[~2018-06-12 2:31 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 [this message]
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
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=83o9ggpwfs.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dancol@dancol.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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).