[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: tex-mode.el dependency on (cl) every?
From: |
David Kastrup |
Subject: |
Re: tex-mode.el dependency on (cl) every? |
Date: |
Mon, 17 Sep 2007 16:36:36 +0200 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/23.0.50 (gnu/linux) |
Stefan Monnier <address@hidden> writes:
>> And why is this needed at all? tex-verbatim-environments is only ever
>> passed to regexp-opt and member, so any old value will be _safe_. So
>> it should be ok just to do
>
>> (put 'tex-verbatim-environments 'safe-local-variable t)
>
> We like `safe-local-variable' to be conservative. To reduce probablity of
> introducing holes in the future.
listp is ok here, I think. Anyway, since in most cases
"safe-local-variable" amounts to "matches type defined by customize"
anyway, why don't we just add something like an explicit ":safe" tag
to our customization types? This could cover part or all of the
customization type, and so everything not matching the "safe" parts of
a customization pattern (including not matching the customize type at
all) would be considered unsafe.
Since the "safe" tag would be a visible part of the customization
type, the likelihood of introducing eval-capable extensions without
thinking about security implications would likely be less than what we
have now.
--
David Kastrup