From: Dan Nicolaescu <dann@ics.uci.edu>
To: Juri Linkov <juri@jurta.org>
Cc: Tom Tromey <tromey@redhat.com>,
"T.V. Raman" <tv.raman.tv@gmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: files.el: Patch to make project-settings optional/customizable
Date: Sat, 22 Nov 2008 11:40:22 -0800 (PST) [thread overview]
Message-ID: <200811221940.mAMJeMpj020419@mothra.ics.uci.edu> (raw)
In-Reply-To: <87zljrh93w.fsf@jurta.org> (Juri Linkov's message of "Sat, 22 Nov 2008 21:08:19 +0200")
Juri Linkov <juri@jurta.org> writes:
> >> So let's get rid of "project" in the function names and use the common
> >> prefix dir-local-variables by analogy with file-local-variables.
> >
> > Sounds OK.
> >
> >> Since the only term the user have to remember will be "directory-local
> >> variables" this suggests using a file name derived from it. Since
> >> the file name should be short a good candidate is ".dir-locals.el".
> >
> > Fine by me,
>
> Done.
Thanks for doing this!
> Since seeing constant file names repeated in several places hurts my eyes,
> I also created defconst for the file name, as Richard suggested - with the
> docstring saying why it is constant.
Since dir-locals-file is used in exactly one function, it would be
better to just let bind it there.
And defconsts are not exactly constants in elisp, so if someone does a
(setq dir-locals-file BLAH), the problem that started this whole
discussion still happens. More, we don't have defconsts for
"Local Variables" or "-*-" which serve a similar purpose but at file
level.
next prev parent reply other threads:[~2008-11-22 19:40 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 14:29 files.el: Patch to make project-settings optional/customizable T.V. Raman
2008-11-13 15:20 ` Chong Yidong
2008-11-13 16:07 ` Dan Nicolaescu
2008-11-13 16:19 ` Dan Nicolaescu
2008-11-13 16:45 ` Tom Tromey
2008-11-13 17:14 ` Chong Yidong
2008-11-13 17:28 ` Dan Nicolaescu
2008-11-13 17:55 ` Juanma Barranquero
2008-11-13 17:59 ` Dan Nicolaescu
2008-11-13 19:13 ` Juanma Barranquero
2008-11-13 19:00 ` Tom Tromey
2008-11-13 19:15 ` Juanma Barranquero
2008-11-13 18:26 ` Chong Yidong
2008-11-13 18:48 ` Dan Nicolaescu
2008-11-18 16:36 ` Dan Nicolaescu
2008-11-18 22:04 ` Juri Linkov
2008-11-18 22:15 ` Dan Nicolaescu
2008-11-18 22:42 ` Juanma Barranquero
2008-11-18 23:18 ` Dan Nicolaescu
2008-11-18 23:41 ` Juanma Barranquero
2008-11-18 22:59 ` Stefan Monnier
2008-11-18 23:31 ` Juri Linkov
2008-11-18 23:33 ` Chong Yidong
2008-11-18 23:41 ` Dan Nicolaescu
2008-11-18 23:50 ` Juanma Barranquero
2008-11-19 0:14 ` Dan Nicolaescu
2008-11-19 1:48 ` Chong Yidong
2008-11-19 8:26 ` Juanma Barranquero
2008-11-19 12:52 ` Richard M. Stallman
2008-11-18 23:37 ` Juanma Barranquero
2008-11-19 2:01 ` Stefan Monnier
2008-11-19 8:39 ` Juanma Barranquero
2008-11-19 13:27 ` Dan Nicolaescu
2008-11-19 22:45 ` Juri Linkov
2008-11-19 22:58 ` Tom Tromey
2008-11-20 2:18 ` Stefan Monnier
2008-11-22 19:08 ` Juri Linkov
2008-11-22 19:40 ` Dan Nicolaescu [this message]
2008-11-22 19:51 ` Juri Linkov
2008-11-22 20:20 ` Dan Nicolaescu
2008-11-22 22:03 ` Juanma Barranquero
2008-11-23 3:34 ` Miles Bader
2008-11-23 5:27 ` Stefan Monnier
2008-11-23 5:36 ` Juanma Barranquero
2008-11-23 5:58 ` Stefan Monnier
2008-11-23 8:10 ` Dan Nicolaescu
2008-11-23 10:45 ` Juri Linkov
2008-11-23 12:10 ` Dan Nicolaescu
2008-11-23 12:41 ` Juanma Barranquero
2008-11-23 17:16 ` Dan Nicolaescu
2008-11-23 17:45 ` Juanma Barranquero
2008-11-23 21:21 ` Dan Nicolaescu
2008-11-24 2:14 ` Stephen J. Turnbull
2008-11-24 3:06 ` Dan Nicolaescu
2008-11-24 5:35 ` Chong Yidong
2008-11-22 4:03 ` Kevin Rodgers
2008-11-19 4:07 ` Stephen J. Turnbull
2008-11-13 19:04 ` Tom Tromey
2008-11-13 19:23 ` Tom Tromey
2008-11-13 19:55 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200811221940.mAMJeMpj020419@mothra.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=monnier@iro.umontreal.ca \
--cc=tromey@redhat.com \
--cc=tv.raman.tv@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.