unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Robin Tarsiger <rtt@dasyatidae.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Rename .dir-locals.el to .dir-locals.eld
Date: Thu, 20 Jan 2022 20:07:58 -0600	[thread overview]
Message-ID: <dda973bf-ef35-9ac0-601a-122861b63475@dasyatidae.com> (raw)
In-Reply-To: <jwvwniugt04.fsf-monnier+emacs@gnu.org>

Stefan Monnier wrote:
> 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?

I think it's a bit late to do that for .dir-locals.el given how many of
them are who-knows-where, but it'd be good to assign them lisp-data-mode
in auto-mode-alist (don't forget the -2 version) and establish a loose
policy of .eld for "read but not evaluated" files for the future.

More specifically to the first part, our only practical option is adding
more names, and the practical utility of the new ones stays questionable
for a long time. High churn and complexity for not much cleanliness. It's
already a special-looking file name, too.

-RTT



  parent reply	other threads:[~2022-01-21  2:07 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
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 [this message]
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=dda973bf-ef35-9ac0-601a-122861b63475@dasyatidae.com \
    --to=rtt@dasyatidae.com \
    --cc=emacs-devel@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).