From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Drew Adams <drew.adams@oracle.com>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: [External] : Rename .dir-locals.el to .dir-locals.eld
Date: Thu, 20 Jan 2022 18:20:32 -0500 [thread overview]
Message-ID: <jwv7daugfm4.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <SJ0PR10MB548874D5B33555C545002F86F35A9@SJ0PR10MB5488.namprd10.prod.outlook.com> (Drew Adams's message of "Thu, 20 Jan 2022 23:14:47 +0000")
>> I think we should restrict the `.el` extension for files which contain
>> actual ELisp code rather than files that just contain text in ELisp's
>> sexp format. WDYT?
>
> 1. Why do you think so?
>
> 2. Isn't every Elisp sexp "code"? How are you
> going to distinguish "code" from other sexps?
Again? We already went through this discussion. And the result is
`lisp-data-mode`, which the major mode I'd recommend we use for
`.eld` files.
Stefan
next prev parent reply other threads:[~2022-01-20 23:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 18:31 Rename .dir-locals.el to .dir-locals.eld Stefan Monnier
2022-01-20 23:14 ` [External] : " Drew Adams
2022-01-20 23:20 ` Stefan Monnier [this message]
2022-01-21 3:04 ` Drew Adams
2022-01-21 1:57 ` Dmitry Gutov
2022-01-21 2:15 ` Robin Tarsiger
2022-01-21 3:04 ` Drew Adams
2022-01-21 3:04 ` Drew Adams
2022-01-21 3:07 ` Dmitry Gutov
2022-01-21 14:17 ` Michael Welsh Duggan
2022-01-21 16:46 ` Drew Adams
2022-01-21 1:22 ` Po Lu
2022-01-21 2:07 ` Robin Tarsiger
2022-01-21 2:20 ` Po Lu
2022-01-21 7:21 ` Eli Zaretskii
2022-01-21 9:49 ` 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=jwv7daugfm4.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
/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).