GNU bug report logs - #51661
29.0.50; What is "interactive Lisp closure"?

Previous Next

Package: emacs;

Reported by: Eli Zaretskii <eliz <at> gnu.org>

Date: Sun, 7 Nov 2021 13:38:02 UTC

Severity: wishlist

Found in version 29.0.50

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


Message #20 received at 51661 <at> debbugs.gnu.org (full text, mbox):

From: Arash Esbati <arash <at> gnu.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 51661 <at> debbugs.gnu.org, Eli Zaretskii <eliz <at> gnu.org>,
 Stefan Monnier <monnier <at> iro.umontreal.ca>
Subject: Re: bug#51661: 29.0.50; What is "interactive Lisp closure"?
Date: Sun, 07 Nov 2021 18:28:47 +0100
Lars Ingebrigtsen <larsi <at> gnus.org> writes:

> Eli Zaretskii <eliz <at> gnu.org> writes:
>
>> No.  But emoji.el says this:
>>
>>       (insert ";; Local" " Variables:
>>   ;; coding: utf-8
>>   ;; version-control: never
>>   ;; no-byte-compile: t
>>   ;; no-update-autoloads: t
>>   ;; End:
>>
>>   (provide 'emoji-labels)
>>
>> and that trips the 'compile-main' target in lisp/Makefile to think
>> this file should not be byte-compiled.
>
> D'oh.  I thought my obfuscation there was sufficient.  I'll get fixing.

you could add a ^L after the function (or better near eof) to prevent
Emacs from parsing that string as a file local variable.  It might be
more clear than further obfuscation (as in 42fd5f2789).

Best, Arash




This bug report was last modified 2 years and 304 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.