unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Arash Esbati <arash@gnu.org>
Cc: 51661@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#51661: 29.0.50; What is "interactive Lisp closure"?
Date: Sun, 07 Nov 2021 22:01:16 +0100	[thread overview]
Message-ID: <87v913el43.fsf@gnus.org> (raw)
In-Reply-To: <86pmrbj2nk.fsf@gnu.org> (Arash Esbati's message of "Sun, 07 Nov 2021 18:28:47 +0100")

Arash Esbati <arash@gnu.org> writes:

> you could add a ^L after the function (or better near eof) to prevent
> Emacs from parsing that string as a file local variable.

I tried that now, but it didn't seem to help.

We really need a general "this thing here shouldn't be interpreted by
any of the things that look for this stuff" mechanism.  But I'm not sure
what that would look like.

(with-uninterpreted-text
  (insert ";; Local Variables:
;; coding: utf-8
;; version-control: never"))

or something?  The code that's looking for these things are pretty
simple, though, and would have to be made more complicated, which is a
downside.

Stefan M's solution (use \s instead of space) is probably the best.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2021-11-07 21:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-07 13:36 bug#51661: 29.0.50; What is "interactive Lisp closure"? Eli Zaretskii
2021-11-07 13:55 ` Lars Ingebrigtsen
2021-11-07 14:06   ` Eli Zaretskii
2021-11-07 14:10     ` Lars Ingebrigtsen
2021-11-07 17:28       ` Arash Esbati
2021-11-07 21:01         ` Lars Ingebrigtsen [this message]
2021-11-07 22:33           ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-07 14:18   ` Andreas Schwab
2022-09-20 12:07 ` Lars Ingebrigtsen

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87v913el43.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=51661@debbugs.gnu.org \
    --cc=arash@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.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).