bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: HOW CAN I STOP THIS NOVICE MODE STUFF?


From: Dan Nicolaescu
Subject: Re: HOW CAN I STOP THIS NOVICE MODE STUFF?
Date: Wed, 02 Jan 2008 16:44:46 -0800

Bruce Korb <address@hidden> writes:

  > Dan Nicolaescu wrote:
  > > It is, please send the list of variables that you have issues with.
  > > If such variables are defined in emacs itself, then the policy is to
  > > determine what type of arguments are safe for the variables. If the
  > > variables are defined in a package, then it is that package's duty to
  > > mark them as safe.
  > 
  > How does "the package" do that?  

Fro example
(put 'VARIABLE_NAME 'safe-local-variable 'integerp)
for a variable that is of type interger. There are many examples of this
in the emacs source code.


  > If the gnulib project doesn't do this, then which package providers
  > actually do know the code?

I can't parse this.


  > > The above is the current policy.
  > > 
  > > Unless you show that the policy is somehow wrong, you'd have trouble
  > > convincing people to change it (which is what you propose).
  > 
  > What I think I am asking for is documentation on how to make this test:
  > 
  >      (eq enable-local-variables :all)
  > 
  > yield "#t" (or however it is spelled in emacs lisp).
  > Would that be:
  > 
  >       (set enable-local-variables  :all)
  > 
  > in my .emacs file?  Another part of my request is that I think it
  > is a little over the top to have to delve into the emacs lisp code
  > to the point were I found the ``(eq enable-local-variables :all)''
  > test at all.  :(

As I said in my previous email there's no way to do this and AFAIK no
desire to do it because it does not seem necessary. If you want this to
change you'd have to show it is necessary.  Precise examples of problems
would be a good start for a proof.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]