unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Juanma Barranquero <lekktu@gmail.com>, Eli Zaretskii <eliz@gnu.org>
Cc: cpitclaudel@gmail.com, "João Távora" <joaotavora@gmail.com>,
	"Stefan Monnier" <monnier@iro.umontreal.ca>,
	"Emacs developers" <emacs-devel@gnu.org>
Subject: Value of `dir-locals-file'   [was: Add a separate mode for .dir-locals.el]
Date: Fri, 18 Oct 2019 14:53:55 +0000 (UTC)	[thread overview]
Message-ID: <c68eeb11-5b18-426a-a9d2-24742c4791b7@default> (raw)

> Too late now, but perhaps .dir-locals.el should have not used the .el extension. Perhaps we should've reserved .el for lisp code (in the usual meaning of the term).

> .dir-locals.el is just a configuration file, even if it contains elisp data. .emacs.desktop is a save file containing real elisp code (I mean, function calls like setq and desktop-create-buffer, not just data lists) and it's not called .emacs-desktop.el, after all. As a consequence, I imagine, of nobody usually either editing or directly loading .emacs.desktop (though I've edited it a few times).

+1.

Same for your bookmarks file.  You can call it
anything, including `foo.el', but the default
name is `.emacs.bmk'.

Maybe someone who named the file `.dir-locals.el'
thought that eventually it might have Lisp code
in it?  Or perhaps this question just wasn't
considered?

Variable `dir-locals-file' is a constant - it's
intended as a variable.  Why is that?  Perhaps
its value should be changed from `.dir-locals.el'?
(Default value, if it becomes a variable variable.)



             reply	other threads:[~2019-10-18 14:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18 14:53 Drew Adams [this message]
2019-10-18 15:03 ` Value of `dir-locals-file' [was: Add a separate mode for .dir-locals.el] Juanma Barranquero

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=c68eeb11-5b18-426a-a9d2-24742c4791b7@default \
    --to=drew.adams@oracle.com \
    --cc=cpitclaudel@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=lekktu@gmail.com \
    --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).