From: Colin Baxter <firstname.lastname@example.org>
To: Ihor Radchenko <email@example.com>
Subject: Re: commit e22b4eb7 kills formatting & color
Date: Mon, 01 Aug 2022 15:34:51 +0100 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <878ro8kqwv.fsf@localhost> (Ihor Radchenko's message of "Mon, 01 Aug 2022 21:57:20 +0800")
>>>>> Ihor Radchenko <email@example.com> writes:
> Colin Baxter <firstname.lastname@example.org> writes:
>> > Do you have any idea which particular file-local variable is >
>> leading to the breakage?
>> Well I'm tempted to say all of them because I have local
>> variables in files and .dir-locals.el in many locations. But for
>> a start:
>> # Local Variables: # eval: (setq org-confirm-babel-evaluate nil)
>> # eval: (setq org-adapt-indentation t) # eval: (set
>> (make-local-variable 'org-hide-emphasis-markers) t) # End:
> I am unable to see any issues with fontification starting from
> emacs -Q and loading a file containing these variables.
I think the solution for me is to delete the .elc files in org-mode. I
am about to do this and will report back.
>> I am obviously missing something because I thought a local
>> variable was by definition local to a file or directory and was
>> not used until that file was opened. So why put them in effect
>> before they are needed?
> They are put into effect after the file is opened, but Org mode is
> not yet loaded. The previous default was applying file-locals
> _after_ Org mode is loaded and hence there was no way to set, for
> example, org-src-fontify-natively or org-enforce-todo-dependencies
> via file-local variables.
Thank you. Now I understand better.
next prev parent reply other threads:[~2022-08-01 14:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 9:44 Colin Baxter
2022-08-01 13:02 ` Ihor Radchenko
2022-08-01 13:21 ` Colin Baxter
2022-08-01 13:57 ` Ihor Radchenko
2022-08-01 14:34 ` Colin Baxter [this message]
2022-08-01 14:51 ` Colin Baxter
2022-08-02 12:49 ` Ihor Radchenko
2022-08-02 13:29 ` Colin Baxter
2022-08-02 13:55 ` Ihor Radchenko
2022-08-02 14:49 ` Colin Baxter
2022-08-03 9:40 ` Ihor Radchenko
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).