Re: Risky local variable mechanism

[Luc Teirlinck]

Chong Yidong wrote:

   I've installed the patch changing the way file local variables are
   handled.  Please see if there are any problems.

I have not yet taken any real look at it, but I believe that @var{(var . val)}
is bad Texinfo.  It believe that it should be @code{(@var{var} . @var{val}}:

===File ~/variables.texi-diff-2=============================
*** variables.texi      13 Feb 2006 19:55:31 -0600      1.72
--- variables.texi      13 Feb 2006 20:00:18 -0600      
***************
*** 1794,1801 ****
  
  @defopt safe-local-variable-values
  This variable provides another way to mark variables as safe.  It is a
! list of cons cells @var{(var . val)}, where @var{var} is a variable
! name and @var{val} is a value of that variable that is safe.
  
  When Emacs asks the user whether or not to obey a set of file variable
  specifications, the user can choose to mark them as safe.  This adds
--- 1794,1801 ----
  
  @defopt safe-local-variable-values
  This variable provides another way to mark variables as safe.  It is a
! list of cons cells @code{(@var{var} . @var{val})}, where @var{var} is
! a variable name and @var{val} is a value of that variable that is safe.
  
  When Emacs asks the user whether or not to obey a set of file variable
  specifications, the user can choose to mark them as safe.  This adds
============================================================