From: Juri Linkov <juri@linkov.net>
To: Mauro Aranda <maurooaranda@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, adam@alphapapa.net, emacs-devel@gnu.org
Subject: Re: Easy Customization for Directory Local Variables
Date: Mon, 02 Oct 2023 19:51:09 +0300 [thread overview]
Message-ID: <86v8bp9dui.fsf@mail.linkov.net> (raw)
In-Reply-To: <3c096b82-cf27-2306-ac25-9d24226685a8@gmail.com> (Mauro Aranda's message of "Mon, 2 Oct 2023 07:06:27 -0300")
>> Or how about cus-edit.el? That's where many/most Customize commands
>> live.
>
> cus-edit.el seems like the better choice for me. When icons were added,
> the functions to customize icons went in there. The only difference
> here is that the new functionality doesn't write to the custom-file,
> rather to some .dir-locals.el.
Agreed.
> Apart from a function that writes to the .dir-locals-2.el file, all
> functions that manipulate the .dir-locals file are from files-x.el. The
> mentioned function is nowhere near smart as modify-dir-local-variable,
> but I had to code it since I didn't find that to be supported in
> files-x.el. Maybe modify-dir-local-variable and the like could be
> taught to handle .dir-locals-2.el too.
files-x.el could have a new function that only writes settings
either to .dir-locals.el or .dir-locals-2.el, with code refactored
out of modify-dir-local-variable.
prev parent reply other threads:[~2023-10-02 16:51 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
2023-10-02 10:06 ` Mauro Aranda
2023-10-02 16:51 ` Juri Linkov [this message]
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=86v8bp9dui.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=adam@alphapapa.net \
--cc=eliz@gnu.org \
--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).