From: Ihor Radchenko <yantar92@gmail.com>
To: rms@gnu.org
Cc: larsi@gnus.org, 57003@debbugs.gnu.org
Subject: bug#57003: 28.1.90; Can local variables be loaded before loading major mode?
Date: Mon, 15 Aug 2022 11:15:01 +0800 [thread overview]
Message-ID: <87k07ayz7u.fsf@localhost> (raw)
In-Reply-To: <E1oNQTp-0006TB-JE@fencepost.gnu.org>
Richard Stallman <rms@gnu.org> writes:
> > Maybe something like 'early-local property instead of 'permanent-local?
> > It will not break the existing cases, while allowing the major modes or
> > users to mark the variables that are safe to load early.
>
> Could you spell out the behavior you propose `early-local' to have?
> From those three lines, I am not sure what it would do.
'early-local will apply file/directory-local variables _before_ executing
the major-mode body. In contrast, the variables without this property
are applied _after_ executing the major-mode body.
Currently, all the file/directory-locals are applied after executing the
major-mode body.
--
Ihor Radchenko,
Org mode contributor,
Learn more about Org mode at https://orgmode.org/.
Support Org development at https://liberapay.com/org-mode,
or support my work at https://liberapay.com/yantar92
next prev parent reply other threads:[~2022-08-15 3:15 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 11:44 bug#57003: 28.1.90; Can local variables be loaded before loading major mode? Ihor Radchenko
2022-08-06 13:06 ` Lars Ingebrigtsen
2022-08-06 13:35 ` Ihor Radchenko
2022-08-06 14:00 ` Visuwesh
2022-08-06 14:34 ` Phil Sainty
2022-08-07 12:44 ` Lars Ingebrigtsen
2022-08-07 13:23 ` Ihor Radchenko
2022-08-07 13:30 ` Lars Ingebrigtsen
2022-08-07 13:52 ` Ihor Radchenko
2022-08-08 11:28 ` Lars Ingebrigtsen
2022-08-08 12:30 ` Ihor Radchenko
2022-08-08 12:35 ` Lars Ingebrigtsen
2022-08-08 12:58 ` Ihor Radchenko
2022-08-08 14:23 ` Lars Ingebrigtsen
2022-08-09 11:29 ` Ihor Radchenko
2022-08-12 12:38 ` Lars Ingebrigtsen
2022-08-13 1:33 ` Phil Sainty
2022-08-13 11:52 ` Lars Ingebrigtsen
2022-08-13 9:02 ` Ihor Radchenko
2022-08-13 11:55 ` Lars Ingebrigtsen
2022-08-13 12:22 ` Ihor Radchenko
2022-08-13 12:32 ` Lars Ingebrigtsen
2022-08-15 3:09 ` Richard Stallman
2022-08-15 3:15 ` Ihor Radchenko [this message]
2022-08-17 2:50 ` Richard Stallman
2022-08-17 10:08 ` Ihor Radchenko
2022-08-29 3:34 ` Richard Stallman
2022-08-31 3:29 ` Ihor Radchenko
2022-10-18 13:29 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-29 6:24 ` Ihor Radchenko
2022-10-29 14:40 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-30 2:57 ` Ihor Radchenko
2022-10-30 3:43 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-30 3:51 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-30 4:01 ` Ihor Radchenko
2022-10-30 12:30 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-31 3:08 ` Ihor Radchenko
2022-10-30 6:59 ` Ihor Radchenko
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=87k07ayz7u.fsf@localhost \
--to=yantar92@gmail.com \
--cc=57003@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=rms@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).