all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@gmail.com>
To: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Cc: 35372@debbugs.gnu.org
Subject: bug#35372: Describe all types of safe-local-variable-values
Date: Sun, 21 Apr 2019 21:58:52 -0400	[thread overview]
Message-ID: <87pnpessv7.fsf@gmail.com> (raw)
In-Reply-To: <87y343fou3.2.fsf@jidanni.org> ("積丹尼 Dan Jacobson"'s message of "Sun, 21 Apr 2019 21:52:04 +0800")

tags 35372 notabug
close 35372
quit

積丹尼 Dan Jacobson <jidanni@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.






      reply	other threads:[~2019-04-22  1:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-21 13:52 bug#35372: Describe all types of safe-local-variable-values 積丹尼 Dan Jacobson
2019-04-22  1:58 ` Noam Postavsky [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pnpessv7.fsf@gmail.com \
    --to=npostavs@gmail.com \
    --cc=35372@debbugs.gnu.org \
    --cc=jidanni@jidanni.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 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.