From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: ola.x.nilsson@axis.com, 45857@debbugs.gnu.org, 30994@debbugs.gnu.org
Subject: bug#30994: bug#45857: 28.0.50; Not possible to set package-user-dir in early-init.el
Date: Thu, 14 Jan 2021 16:02:30 -0500 [thread overview]
Message-ID: <jwv7dofs0nd.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83h7njb6a5.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 14 Jan 2021 22:41:22 +0200")
> Thanks, I actually meant to have that in the sources in some prominent
> place.
Ah, OK, I'll do that.
>> Currently we solve this by calling `custom-reevaluate-setting` twice for
>> every one of those variables. But it means that we silently override
>> any change made to those variables from `early-init.el`.
>>
>> As noted, the only var whose default value needs to be (re)computed
>> after loading `early-init.el` is `blink-cursor-mode`. In theory there
>> could be more, but I think we should aim to reduce rather than increase
>> those cases.
>
> I think relying on a small number of such variables is not
> future-proof enough. This case is a living proof: we decided
> something 2 years ago, but changes we did since then require us now to
> change that decision, which means we risk bumping into issues which we
> wanted to avoid back then. That's a general problem with kludgey
> solutions.
Indeed. Other than eliminate the `blink-cursor-mode` special case,
I can't see how to make it less kludgey.
> I think we need some new infrastructure that would support the two
> init files that are loaded in different stages of startup.
>
> Basically, some variables can only be usefully initialized after some
> part(s) of startup have happened already. One way of dealing with
> this is to have the variables record this information (e.g., in a
> plist of their symbol) that would allow us evaluate each variable only
> once, at the earliest opportunity where the prerequisites are
> fulfilled.
In theory I would agree, but:
- We don't have any such system to record dependencies, so we'd have to
design and implement it. A minimal version would simply duplicate
`customize-initialize-delayed` into two different options depending on
the stage at which we should initialize it, but that'd still be pretty
ad-hoc.
- The only need for this complexity is `blink-cursor-mode` and it's only
needed because we currently handle `blink-cursor-mode` incorrectly.
So, I'd rather fix the bug and avoid the complexity.
>> E.g. the current way `blink-cursor-mode` is defined means that if I
>> start `emacs -Q -nw` and later create a GUI frame, that frame won't
>> have a blinking cursor. I think this is a bug (tho I can see that
>> some people may consider it a feature if they (like me) dislike
>> blinking cursors ;-0)
> I think that's a separate issue.
Agreed, which is why the patch I propose keeps this for later.
Stefan
next prev parent reply other threads:[~2021-01-14 21:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 11:51 bug#45857: 28.0.50; Not possible to set package-user-dir in early-init.el Ola x Nilsson
2021-01-14 15:03 ` Stefan Monnier
2021-01-14 15:41 ` Stefan Monnier
2021-01-14 18:20 ` Stefan Monnier
2021-01-14 18:40 ` bug#30994: " Eli Zaretskii
2021-01-14 19:32 ` Stefan Monnier
2021-01-14 20:41 ` Eli Zaretskii
2021-01-14 21:02 ` Stefan Monnier [this message]
2021-01-15 7:52 ` Eli Zaretskii
2021-01-15 16:08 ` Stefan Monnier
2021-01-15 18:25 ` Eli Zaretskii
2021-01-15 22:19 ` Stefan Monnier
2021-01-16 4:52 ` Stefan Monnier
2021-01-19 17:11 ` Stefan Monnier
2021-01-22 16:08 ` bug#30994: " Phillip Lord
2021-01-22 16:44 ` Stefan Monnier
2021-01-22 17:02 ` Phillip Lord
2021-01-16 7:08 ` 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=jwv7dofs0nd.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=30994@debbugs.gnu.org \
--cc=45857@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=ola.x.nilsson@axis.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).