bug#343: marked as done (C mode asks twice about local variables)

[Emacs bug Tracking System]

Your message dated Thu, 31 Jul 2008 10:14:42 -0400
with message-id <871w1aywbx.fsf@stupidchicken.com>
and subject line Re: C mode asks twice about local variables
has caused the Emacs bug report #343,
regarding C mode asks twice about local variables
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact don@donarmstrong.com
immediately.)


-- 
343: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=343
Emacs Bug Tracking System
Contact don@donarmstrong.com with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> C mode asks twice about local variables
>
>
>
>
> Date: 
>
> Sat, 31 May 2008 18:51:35 -0400
>
>
>
>
> User-agent: 
>
> Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/)
>
>
>
>
> This applies in Emacs 22.2 and CVS trunk.
>
> emacs -Q lib-src/etags.c
>
>     The local variables list in etags.c
>     contains values that may not be safe (*).
>
>     Do you want to apply it?  You can type
>     y  -- to apply the local variables list.
>     n  -- to ignore the local variables list.
>     !  -- to apply the local variables list, and permanently mark these
>     values (*) as safe (in the future, they will be set automatically.)
>
>     indent-tabs-mode: t
>     tab-width: 8
>     fill-column: 79
>   * c-font-lock-extra-types: ("FILE" "bool" "language" "linebuffer" "fdesc" 
> "node" "regexp")
>     c-file-style: "gnu"
>
>
> If I answer `y', nothing happens. I have to press `y' a second time.
>
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: C mode asks twice about local variables
>
>
>
>
> Date: 
>
> Thu, 31 Jul 2008 10:14:42 -0400
>
>
>
>
> I believe this is now fixed in the trunk.  We'll leave it unfixed in the
> branch, since the fix involves the hack-local-variables code and needs
> to be tested thoroughly.
>
>
> --- End Message ---