unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: 57994@debbugs.gnu.org
Subject: bug#57994: 29.0.50; .dir-locals.el
Date: Thu, 22 Sep 2022 08:17:32 +0300	[thread overview]
Message-ID: <83k05wt2c3.fsf@gnu.org> (raw)
In-Reply-To: <E1obCdX-0003Wj-7p@fencepost.gnu.org> (message from Richard Stallman on Wed, 21 Sep 2022 23:12:27 -0400)

tags 57994 notabug
thanks

> From: Richard Stallman <rms@gnu.org>
> Date: Wed, 21 Sep 2022 23:12:27 -0400
> 
> When I open in Emacs any file in Master, such as `BUGS', `.dir-locals'
> itself, `COPYING', or `src/emacs.c', it asks me to approve the list of local
> variables specified in `.dir-locals'.
> 
> It says that `vc-git-annotate-switches' and
> `diff-add-log-use-relative-names' are unsafe.
> 
> ((nil . ((tab-width . 8)
>          (sentence-end-double-space . t)
>          (fill-column . 70)
> 	 (emacs-lisp-docstring-fill-column . 65)
>          (vc-git-annotate-switches . "-w")
>          (bug-reference-url-format . "https://debbugs.gnu.org/%s")
> 	 (diff-add-log-use-relative-names . t)))

This is not a bug.  These variables were recently added to our
.dir-locals.el, and they have appropriate safe-variable properties
that prevent the prompt -- but only as long as you use a recent enough
build of Emacs.  If you update from Git, but don't rebuild Emacs after
the update, or if you use an older version of Emacs produced not from
the master branch, you will see those prompts.  For those cases where
you don't use a recent-enough build of Emacs, if you don't want to see
these prompts each time you visit some file in the repository, you can
add this to your ~/.emacs init file:

  (put 'diff-add-log-use-relative-names 'safe-local-variable 'booleanp)
  (put 'vc-git-annotate-switches 'safe-local-variable 'stringp)





  parent reply	other threads:[~2022-09-22  5:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22  3:12 bug#57994: 29.0.50; .dir-locals.el Richard Stallman
2022-09-22  5:00 ` Sean Whitton
2022-09-22  5:17 ` Eli Zaretskii [this message]
2022-09-23 16:18   ` Lars Ingebrigtsen

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=83k05wt2c3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=57994@debbugs.gnu.org \
    --cc=rms@gnu.org \
    /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).