all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: maurooaranda@gmail.com, adam@alphapapa.net, emacs-devel@gnu.org
Subject: Re: Easy Customization for Directory Local Variables
Date: Mon, 02 Oct 2023 10:21:14 +0300	[thread overview]
Message-ID: <83y1gl7amt.fsf@gnu.org> (raw)
In-Reply-To: <86jzs5r0b9.fsf@mail.linkov.net> (message from Juri Linkov on Mon, 02 Oct 2023 09:43:54 +0300)

> From: Juri Linkov <juri@linkov.net>
> Cc: maurooaranda@gmail.com,  adam@alphapapa.net,  emacs-devel@gnu.org
> Date: Mon, 02 Oct 2023 09:43:54 +0300
> 
> >> There is no single prefix in files-x.el, but still names are quite
> >> consistent.  So you could choose any prefix you think would be
> >> internally consistent between all your new functions and variables.
> >
> > Why should this be in files-x.el? why not in custom.el, for example?
> 
> If these functions implement a new customization type then
> a good place would be in custom.el indeed.  Only functions
> that write the dir-locals file could remain in files-x.el.

Or how about cus-edit.el?  That's where many/most Customize commands
live.



  reply	other threads:[~2023-10-02  7:21 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
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 [this message]
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=83y1gl7amt.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=adam@alphapapa.net \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    --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.