From: "Ken Manheimer" <ken.manheimer@gmail.com>
Cc: emacs-devel@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
rms@gnu.org
Subject: Re: allout patch - more safe-local-variables, plus autoloads
Date: Fri, 21 Apr 2006 11:39:13 -0400 [thread overview]
Message-ID: <2cd46e7f0604210839q4597d83aied8b4251ea761a70@mail.gmail.com> (raw)
In-Reply-To: <85mzefoti5.fsf@lola.goethe.zz>
On 4/21/06, David Kastrup <dak@gnu.org> wrote:
> "Ken Manheimer" <ken.manheimer@gmail.com> writes:
>
> > in many cases, the qualifying criteria is already present, in the form
> > of the custom-type information:
> >
> > seems to me we're heading down the road of duplicating the mechanisms
> > of the custom type system, and that we should be using it. i strongly
> > suspect that the custom types of customizable variables are
> > appropriate as safety criteria in many cases, as well. we wouldn't
> > want to assume that, but i suspect it would be very useful to make it
> > easy for authors to use the custom-type criteria for this purpose.
>
> I don't see that. If a variable can be dangerous, I think it very
> unlikely that all uses conforming to its customization type would be
> harmless.
why not? seems to me that the customization criteria are in
substantial part about safety - a good author is preventing their
users from shooting themselves in the foot with problematic custom
values. the only difference is that less attention is likely to be
paid to users who are deviously *trying* to blow their foot off.-) (i
wonder how often current safety tests exceed their variable's
customization tests, when present? i suspect not many.)
the crucial thing is that the safety criteria should never *conflict*
with the customization criteria, and in fact, should always obtain for
it. it may be that people need to be thinking more stringently about
their customization criteria, but the safety concerns apply there as
much as anywhere.
i could be wrong here - counter examples welcome. for what it's
worth, it happens to work quite nicely for allout's variables.
--
ken manheimer
ken.manheimer@gmail.com
http://myriadicity.net
next prev parent reply other threads:[~2006-04-21 15:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-17 19:11 allout patch - more safe-local-variables, plus autoloads Ken Manheimer
2006-04-18 12:57 ` Richard Stallman
2006-04-18 13:18 ` Stefan Monnier
2006-04-19 4:17 ` Richard Stallman
2006-04-19 4:39 ` Stefan Monnier
2006-04-19 21:12 ` Richard Stallman
2006-04-20 2:47 ` Luc Teirlinck
2006-04-20 17:34 ` Stefan Monnier
2006-04-21 13:07 ` Richard Stallman
2006-04-21 15:02 ` Ken Manheimer
2006-04-21 15:09 ` David Kastrup
2006-04-21 15:39 ` Ken Manheimer [this message]
2006-04-21 17:15 ` Stefan Monnier
2006-04-24 21:19 ` Ken Manheimer
2006-04-19 23:08 ` Ken Manheimer
2006-04-20 10:35 ` Richard Stallman
2006-04-20 18:49 ` autoloads for safe-local-variables (was: allout patch - more safe-local-variables, plus autoloads) Reiner Steib
2006-04-20 19:52 ` autoloads for safe-local-variables (was: allout patch - moresafe-local-variables, " Stuart D. Herring
2006-04-21 13:07 ` autoloads for safe-local-variables (was: allout patch - more safe-local-variables, " Richard Stallman
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=2cd46e7f0604210839q4597d83aied8b4251ea761a70@mail.gmail.com \
--to=ken.manheimer@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--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).