From: Drew Adams <drew.adams@oracle.com>
To: Mauro Aranda <maurooaranda@gmail.com>, Adam Porter <adam@alphapapa.net>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: [External] : Re: Easy Customization for Directory Local Variables
Date: Mon, 25 Sep 2023 16:18:15 +0000 [thread overview]
Message-ID: <CO6PR10MB547303120689A2AE205D886DF3FCA@CO6PR10MB5473.namprd10.prod.outlook.com> (raw)
In-Reply-To: <969c85af-2d2d-bb06-8b36-fd16ba8339f8@gmail.com>
> The main command, currently called customize-dirlocals, creates a buffer
> to edit a .dir-locals.el file under default-directory. No limitation
> about a "project", as handled by project.el, or whatsoever. At least
> that's the goal.
>
> Another command, currently called customize-dirlocals-project, creates
> a buffer to edit the .dir-locals.el file that belongs to some "project",
> again, as handled by project.el. I'm not much of a user of project.el
> but it's supposed to be handy, since the user might be editing a file
> under a subdirectory of a "project" (recognized by project.el) and
> decides to edit the .dir-locals.el that belongs to that "project". So I
> can see why it would be desired for such command to be in project.el,
> just like commands to customize a specific set of options, or a group,
> belong outside cus-edit.el
I see. Sorry for the noise. I didn't realize
this was really project-specific. I was thinking
it was what you describe for `customize-dirlocals'.
next prev parent reply other threads:[~2023-09-25 16:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-24 13:13 Easy Customization for Directory Local Variables Mauro Aranda
2023-09-25 2:20 ` Adam Porter
2023-09-25 10:17 ` Mauro Aranda
2023-09-25 14:32 ` [External] : " Drew Adams
2023-09-25 15:17 ` Mauro Aranda
2023-09-25 16:18 ` Drew Adams [this message]
2023-09-25 17:40 ` Juri Linkov
2023-09-26 22:02 ` Dmitry Gutov
2023-10-01 13:37 ` Mauro Aranda
2023-10-01 18:49 ` Juri Linkov
2023-10-02 5:41 ` Eli Zaretskii
2023-10-02 6:43 ` Juri Linkov
2023-10-02 7:21 ` Eli Zaretskii
2023-10-02 10:06 ` Mauro Aranda
2023-10-02 16:51 ` Juri Linkov
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=CO6PR10MB547303120689A2AE205D886DF3FCA@CO6PR10MB5473.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=adam@alphapapa.net \
--cc=emacs-devel@gnu.org \
--cc=maurooaranda@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 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).