unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Mauro Aranda <maurooaranda@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 66663@debbugs.gnu.org, juri@linkov.net
Subject: bug#66663: 30.0.50; Allow dir locals file selection in *-dir-local-variable functions
Date: Sat, 21 Oct 2023 10:49:26 -0300	[thread overview]
Message-ID: <514ef416-843b-4b80-abcf-cb4621b4b58d@gmail.com> (raw)
In-Reply-To: <83o7gsqh3i.fsf@gnu.org>

On 21/10/23 09:45, Eli Zaretskii wrote:
 >> Cc: Juri Linkov <juri@linkov.net>
 >> Date: Sat, 21 Oct 2023 09:16:28 -0300
 >> From: Mauro Aranda <maurooaranda@gmail.com>
 >>
 >> +Since both @file{.dir-locals.el} and @file{.dir-locals-2.el} file
 >> +might exist in the same directory, there may be some clash about which
 >> +file you want to modify when executing the above three commands.  To
 >> +solve that, all three of them take a prefix argument, to indicate
 >> +which file you want to modify.  When both files exist, a prefix
 >> +argument means to prefer to modify @file{.dir-locals.el} instead of
 >> +@file{.dir-locals-2.el}.  When one of the files doesn't exist, and
 >> +you're adding a variable or copying the file-local variables, a prefix
 >> +argument means to modify (i.e., create) the file that doesn't yet
 >> +exist.
 >
 > I think a better UI is to ask the user when the command is invoked
 > with a prefix argument.

Yes, that makes sense.  I'll try that approach.





  reply	other threads:[~2023-10-21 13:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-21 12:08 bug#66663: 30.0.50; Allow dir locals file selection in *-dir-local-variable functions Mauro Aranda
2023-10-21 12:16 ` Mauro Aranda
2023-10-21 12:45   ` Eli Zaretskii
2023-10-21 13:49     ` Mauro Aranda [this message]
2023-10-21 14:06       ` Mauro Aranda
2023-10-21 18:21         ` Juri Linkov
2023-10-21 22:10           ` Mauro Aranda
2023-10-22 17:55             ` 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=514ef416-843b-4b80-abcf-cb4621b4b58d@gmail.com \
    --to=maurooaranda@gmail.com \
    --cc=66663@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=juri@linkov.net \
    /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).