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: Wed, 31 Aug 2022 11:29:08 +0800 [thread overview]
Message-ID: <87o7w1ozuj.fsf@localhost> (raw)
In-Reply-To: <E1oSVXx-0008BG-HH@fencepost.gnu.org>
Richard Stallman <rms@gnu.org> writes:
> That's the right thing to do. However, your previous message seemed
> to imply a problem, because it proposed loading these buffer-local
> variables "before executing the major mode body", and that would be
> before `kill-all-local-variables'. That function would kill these new
> bindings, unless it were prevented from doing so.
I was referring to define-derived-mode macro, where
`kill-all-local-variables' is actually called before BODY argument. Of
course, as Lars pointed, some major modes may not use
`define-derived-mode' and the meaning of "body" is different.
The major modes that do not use define-derived-mode are actually
problematic. While we can expect `kill-all-local-variables' to be called
early even in such major modes, the mode symbol is not yet known by the
time `kill-all-local-variables' is called. I am not sure how to approach
the proposed 'early-local property for mode-specific
file/directory-local variables in such scenario.
--
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-31 3:29 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o7w1ozuj.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.