[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Risky local variable mechanism
From: |
David Kastrup |
Subject: |
Re: Risky local variable mechanism |
Date: |
Thu, 02 Feb 2006 10:54:12 +0100 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) |
"Richard M. Stallman" <address@hidden> writes:
> If you want to be really restrictive, you can introduce a list of
> `safe-local-variables', and prompt for anything outside that list (the
> prompt could have an additional choice, [(a) always allow this
> variable], a variable to the list).
>
> Perhaps that is the best solution. However, if only 2% of all file
> local variable settings are outside that list, it will still cause
> annoyance to a lot of people.
>
> So let's first see if some more general method based on custom types
> can be made to work. If that can't be made to work, we can fall back
> on this approach.
I agree with others that this is not something that makes sense to try
to push into Emacs 22.1. I'd even be hesitant to have it move into
23.1: I think that 23.1 should basically concentrate on pushing out
multi-tty and unicode-2 branches, as well as an update of frozen
externally maintained packages (like tramp).
Once we have that off our chest, there is a better time to work on
what clearly is a new feature requiring lots of testing and
experiments.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
- Re: Risky local variable mechanism, Jonathan Yavner, 2006/02/01
- Re: Risky local variable mechanism, Richard M. Stallman, 2006/02/01
- Re: Risky local variable mechanism, Kim F. Storm, 2006/02/02
- Re: Risky local variable mechanism, Kim F. Storm, 2006/02/02
- Re: Risky local variable mechanism, Richard M. Stallman, 2006/02/03
- Re: Risky local variable mechanism, Luc Teirlinck, 2006/02/03
- Re: Risky local variable mechanism, Richard M. Stallman, 2006/02/05
- Re: Risky local variable mechanism, Luc Teirlinck, 2006/02/06
- Re: Risky local variable mechanism, Richard M. Stallman, 2006/02/07