From: Colin Baxter <email@example.com>
To: Ihor Radchenko <firstname.lastname@example.org>
Subject: Re: commit e22b4eb7 kills formatting & color
Date: Tue, 02 Aug 2022 14:29:45 +0100 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <871qtylsjj.fsf@localhost> (Ihor Radchenko's message of "Tue, 02 Aug 2022 20:49:04 +0800")
>>>>> Ihor Radchenko <firstname.lastname@example.org> writes:
> Colin Baxter <email@example.com> writes:
>> No, I spoke too soon. That is not the answer. For me using "emacs
>> -q", an opened org file will expand the folds using <TAB> but
>> there is still no synatx coloring. This is probably not relevant
>> but my system is 32bit not 64.
> Hmm. I was able to reproduce the issue using some slightly
> non-standard settings. However, only when there is a popup window
> asking about non-safe file-local variables. Does it also happen
> for you after such a popup? Or do you have the settings marked
I disable popups so I always receive a buffer with:
The local variables list in test.org
or .dir-locals.el contains values that may not be safe (*).
Do you want to apply it? You can type
y -- to apply the local variables list.
n -- to ignore the local variables list.
! -- to apply the local variables list, and permanently mark these
values (*) as safe (in the future, they will be set automatically.)
i -- to ignore the local variables list, and permanently mark these
values (*) as ignored
I then enter "y". It's a habit of mine never to use "!" even for files I
use every day. I cannot remember ever entering "n" or "i".
next prev parent reply other threads:[~2022-08-02 13:31 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
2022-08-01 14:51 ` Colin Baxter
2022-08-02 12:49 ` Ihor Radchenko
2022-08-02 13:29 ` Colin Baxter [this message]
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).