all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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 14:32:13 +0000	[thread overview]
Message-ID: <CO6PR10MB547347596DEF0A5FACB4151CF3FCA@CO6PR10MB5473.namprd10.prod.outlook.com> (raw)
In-Reply-To: <8fd3190a-c401-e650-b851-063d430673d3@gmail.com>

 
>> From a quick look, my only suggestion is to have the project command be named something like `project-edit-dir-local-variables'.
> 
> That would mean to add it to project.el.  I'm fine with proposing that
> provided the code gets accepted.

Are dir-local vars limited to what Emacs
calls a "project"?  I didn't think so.
Emacs's use of the term "project" is more
limited than what a project might be in
general, and even that is, I think, more
limited than what dir-local vars are/imply.

(Just one top-of-the-head opinion, and not
one very knowledgeable about Emacs "projects".)

  reply	other threads:[~2023-09-25 14:32 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     ` Drew Adams [this message]
2023-09-25 15:17       ` [External] : " Mauro Aranda
2023-09-25 16:18         ` Drew Adams
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CO6PR10MB547347596DEF0A5FACB4151CF3FCA@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 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.