unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Michael Welsh Duggan <mwd@md5i.com>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	Dmitry Gutov <dgutov@yandex.ru>
Subject: RE: [External] : Rename .dir-locals.el to .dir-locals.eld
Date: Fri, 21 Jan 2022 16:46:20 +0000	[thread overview]
Message-ID: <SJ0PR10MB548872D0B99F9AA5B2A1753AF35B9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87r191fa1q.fsf@md5i.com>

> > I think you're talking about Lisp code that's
> > Lisp-`read'able without error, but not
> > necessarily `eval'able without error.
> >
> > If so, fine.  But that, in itself, doesn't
> > say why it merits a different file extension.
> > There may be good reasons.  So far, haven't
> > heard any.
> 
> From my point of view, it is an indication that the lisp forms in the
> file are not guaranteed to be (and most likely will not be) evaluated.
> Having a separate mode means that buffers with this mode can
> automatically avoid linting as if they were top level forms intended for
> evaluation.  Having a separate extension makes it easy to automatically
> use a different editing mode.  Also, the extension and mode are good
> indicators to the user that any forms generally meant for evaluation
> (like backquote) are not guaranteed to enter a context in which they
> will be evaluated.
> 
> All of this is just my opinion.  I did not go back and reread the
> discussion that led to lisp-data-mode.  I remember that I was swayed by
> the reasons in that discussion, so the reasons I state above may not be
> good enough to merit the change in your opinion.

Thank you.  And congratulations on being the
first (and so far only) one to present reasons
in favor of the proposed file-extension change.

Seriously.  Whether it's the White House or
some other bike shed, saying why & why not
paint it green helps the discussion.



  reply	other threads:[~2022-01-21 16:46 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 [this message]
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=SJ0PR10MB548872D0B99F9AA5B2A1753AF35B9@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=mwd@md5i.com \
    /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).