GNU bug report logs - #35372
Describe all types of safe-local-variable-values

Previous Next

Full log

View this message in rfc822 format

From: Noam Postavsky <npostavs <at> gmail.com>
To: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
Cc: 35372 <at> debbugs.gnu.org
Subject: bug#35372: Describe all types of safe-local-variable-values
Date: Sun, 21 Apr 2019 21:58:52 -0400

tags 35372 notabug
close 35372
quit

積丹尼 Dan Jacobson <jidanni <at> jidanni.org> writes:

> "safe-local-variable-values is a variable defined in ‘files.el’.
>
> List variable-value pairs that are considered safe.
> Each element is a cons cell (VAR . VAL)..."
>
> No,only a few are like that
>
> x((eval picture-movement-down)

That's an alternate way of writing (eval . (picture-movement-down))

> x (eval register-file-header-action "// @version[ 	]* " 'update-write-count)

(eval . (register-file-header-action "// @version[ 	]* " 'update-write-count))

>   (dired-omit-mode . t)
>   (picture-vertical-step . 1)
>   (picture-horizontal-step . 0)
>   (sh-indentation . 2)
>   (dired-actual-switches . "-ogta")
>   (dired-actual-switches . "-ogt")
>   (dired-actual-switches . "-og")
>   (truncate-lines . 1)
> y (make-backup-files))

(make-backup-files . nil)

> Others either don't have a "." (x), or don't have a ". VAL" (y).
>
> So the docstring should explain them too.

There's no sense in every alist docstring explaining dot notation.

See (elisp) Dotted Pair Notation.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.