From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 58486@debbugs.gnu.org, Philip Kaludercic <philipk@posteo.net>,
Stefan Kangas <stefan@marxist.se>
Subject: bug#58486: [PATCH] Prevent .dir-locals.el from being byte-compiled
Date: Fri, 14 Oct 2022 12:32:12 -0400 [thread overview]
Message-ID: <jwva65yfjyd.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <865ygn4pno.fsf@mail.linkov.net> (Juri Linkov's message of "Thu, 13 Oct 2022 20:18:43 +0300")
>>> When selecting a number of .el files in Dired and byte-compiling them
>>> I'll usually also select a .dir-locals.el file that won't compile.
>>> Would annotating them as non-byte-compilable files be sensible?
>>
>> Makes sense to me, FWIW. Though Stefan M might point out that these
>> files should actually be called ".dir-locals.eld". Which, BTW, we
>> should probably add support for. And "*.eld" files should never be
>> compiled, I think?
>
> It's already handled by auto-mode-alist:
>
> (defvar auto-mode-alist
> ...
> ;; .dir-locals.el is not really Elisp. Could use the
> ;; `dir-locals-file' constant if it weren't defined below.
> ("\\.dir-locals\\(?:-2\\)?\\.el\\'" . lisp-data-mode)
To stay in the spirit of bug#58075, if we consider the major mode
specified in `auto-mode-alist` (and `mode:` cookies) as a proxy for
"file type", maybe we should arrange to try and avoid byte-compiling
those `.el` files whose major mode is `lisp-data-mode` (or: is not
`emacs-lisp-mode`)?
Stefan
next prev parent reply other threads:[~2022-10-14 16:32 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 9:05 bug#58486: [PATCH] Prevent .dir-locals.el from being byte-compiled Philip Kaludercic
2022-10-13 14:20 ` Stefan Kangas
2022-10-13 14:32 ` Philip Kaludercic
2022-10-13 14:51 ` Stefan Kangas
2022-10-13 17:18 ` Juri Linkov
2022-10-13 19:11 ` Philip Kaludercic
2022-10-14 9:22 ` bug#58506: Use ".dir-locals.eld" and ".dir-locals-2.eld" when they exist Stefan Kangas
2022-10-14 10:38 ` Eli Zaretskii
2022-10-14 12:36 ` Stefan Kangas
2022-10-14 11:25 ` Lars Ingebrigtsen
2022-10-14 12:36 ` Stefan Kangas
2022-10-14 13:04 ` Robert Pluim
2022-10-14 13:10 ` Lars Ingebrigtsen
2022-10-14 13:23 ` Robert Pluim
2022-10-14 13:29 ` Lars Ingebrigtsen
2022-10-14 13:41 ` Robert Pluim
2022-10-14 15:13 ` Philip Kaludercic
2022-10-15 9:18 ` Lars Ingebrigtsen
2022-10-15 9:38 ` Philip Kaludercic
2022-10-15 9:42 ` Lars Ingebrigtsen
2022-10-15 10:00 ` Lars Ingebrigtsen
2022-10-15 11:35 ` Philip Kaludercic
2022-10-15 13:56 ` Lars Ingebrigtsen
2022-10-15 15:12 ` Philip Kaludercic
2022-10-15 16:22 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-16 8:39 ` Lars Ingebrigtsen
2022-10-15 10:05 ` Stefan Kangas
2022-10-15 15:19 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-16 8:47 ` Lars Ingebrigtsen
2022-10-16 9:34 ` Philip Kaludercic
2022-10-16 9:43 ` Lars Ingebrigtsen
2022-10-16 13:38 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-16 13:44 ` Lars Ingebrigtsen
2022-10-18 13:30 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-18 7:28 ` Juri Linkov
2022-10-18 13:25 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-14 13:38 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-14 15:07 ` Philip Kaludercic
2022-10-14 16:32 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-10-15 19:16 ` bug#58486: [PATCH] Prevent .dir-locals.el from being byte-compiled Juri Linkov
2022-10-16 13:17 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 18:02 ` Lars Ingebrigtsen
2022-10-14 18:14 ` Philip Kaludercic
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=jwva65yfjyd.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=58486@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=monnier@iro.umontreal.ca \
--cc=philipk@posteo.net \
--cc=stefan@marxist.se \
/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).