From: "Fraga, Eric" <e.fraga@ucl.ac.uk>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: Emacs Org mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: folding problems
Date: Thu, 4 Aug 2022 15:10:23 +0000 [thread overview]
Message-ID: <87fsichwo0.fsf@ucl.ac.uk> (raw)
In-Reply-To: <871qtwqdqk.fsf@localhost> (Ihor Radchenko's message of "Thu, 04 Aug 2022 22:34:27 +0800")
Maybe unrelated but I will add that the recent changes to how local
variables are processed is breaking my usage of org quite seriously. To
be clear: I am not complaining: it's my fault for tracking the bleeding
edge of development for both org and Emacs. 😉 But I thought I would
mention what I am seeing just in case it's useful.
An example: when exporting a long document which has many src blocks,
each of those blocks is now being loaded and local variables (which
include dir local variables) are being evaluated (which they were not
before, I guess?). I don't know if this is an org change or an Emacs
change?
The src blocks are likely loaded by org because I am using engraved for
formatting the src blocks on export. This is a nightmare if any of the
variables are considered unsafe as it requires confirmation for each
such case.
And if some src block mode needs a special input method, this is causing
the export to fail:
activate-input-method: Can’t activate input method ‘TeX’
although I am not sure, at this point, where/when this is happening.
And, no, unfortunately I don't know if emacs -Q solves these issues. I
did try and it does seem like the local variable aspect happens; it's
just that my export is so tailored that other things break for not being
defined in emacs -Q and so I cannot fully export my document.
I will need to revert to an older version of org as I need to get work
done. There's too much breaking to spend the time at the moment
investigating. 😕 But no worries: that's what git is for! 👍
Thank you,
eric
PS -if any of the above is the fault of changes to Emacs, I will post on
the devel list.
--
: Eric S Fraga, with org release_9.5.4-706-g4702a7 in Emacs 29.0.50
next prev parent reply other threads:[~2022-08-04 15:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 13:24 folding problems Fraga, Eric
2022-08-04 14:34 ` Ihor Radchenko
2022-08-04 14:46 ` Fraga, Eric
2022-08-04 15:10 ` Fraga, Eric [this message]
2022-08-05 1:45 ` Ihor Radchenko
2022-08-05 9:35 ` Fraga, Eric
2022-08-05 11:37 ` Ihor Radchenko
2022-08-05 12:16 ` Fraga, Eric
2022-08-05 13:55 ` Fraga, Eric
2022-08-04 16:23 ` Fraga, Eric
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fsichwo0.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@gmail.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/org-mode.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).