On 20/12/2024 04:37, Joseph Turner wrote:
Max Nikulin writes:
Have you tried to create a comment block below?
#+begin_comment
Deactivate local variables above in the example block:
Local Variables:
End:
#+end_comment
In my testing, in order to make Emacs ignore the `foo: bar' binding, the
empty Local Variables list actually needs to go first.
Then it is more fragile in the case of complex documents, but still may
be viable for simple ones with single example.
Splitting the example into two parts results in "File mode specification
error: (user-error Local variables entry is missing the prefix) " upon
opening the file.
I expected that the code looking up for local variables is reasonably shy.
You can test with this:
#+BEGIN_SRC org
# Local Variables:
#+END_SRC
#+BEGIN_SRC org
# org-srs-review-new-items-per-day: 30
# org-srs-review-max-reviews-per-day: 100
# End:
#+END_SRC
Unfortunately
: # Local Variables:
#+BEGIN_EXAMPLE
# org-srs-review-new-items-per-day: 30
# org-srs-review-max-reviews-per-day: 100
# End:
#+END_EXAMPLE
Causes a warning as well:
"Local variables list is not properly terminated"
(info "(emacs) Specifying File Variables")
By the way, is there a built-in command to copy that (info ...) sexp
when viewing that info page?
A short answer "C-0 c" or "C-0 w". Maybe I will send a longer one,
dropping bohonghuang from Cc.
<https://www.gnu.org/software/emacs/manual/html_node/emacs/Specifying-File-Variables.html>
Thanks, I just re-read that page more carefully, and I see this:
If some unrelated text might look to Emacs as a local variables
list, you can countermand that by inserting a form-feed character (a
page delimiter, *note Pages::) after that text. Emacs only looks for
file-local variables in the last page of a file, after the last page
delimiter.
I do not like non-printable characters. E.g. Thunderbird rendered your
message with confusingly large vertical space in the middle. Outside of
Emacs, kludges like ";;; org.el ends here" are not common. I would not
be surprised by some issues on attempt to edit the README.org file on
the GitHub site directly.
