unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andy Moreton <andrewjmoreton@gmail.com>
Cc: 23476@debbugs.gnu.org
Subject: bug#23476: 25.0.93; Visiting C files on master signals an error
Date: Sat, 07 May 2016 20:32:20 +0300	[thread overview]
Message-ID: <83oa8hepuj.fsf@gnu.org> (raw)
In-Reply-To: <867ff56cpr.fsf@gmail.com> (message from Andy Moreton on Sat, 07 May 2016 17:43:12 +0100)

> From: Andy Moreton <andrewjmoreton@gmail.com>
> Date: Sat, 07 May 2016 17:43:12 +0100
> 
> On Sat 07 May 2016, Eli Zaretskii wrote:
> 
> > If you visit any C file on the master branch with Emacs 25.0.93, Emacs
> > asks an annoying question about unsafe local variables:
> >
> >
> >
> >
> > If you answer "y", Emacs signals an error:
> >
> >   File local-variables error: (void-function c-make-noise-macro-regexps)
> >
> > If I do the same with Emacs built from master, the problem doesn't
> > happen.  Did someone assume that the sources on master are only edited
> > by an Emacs produced from that master?  If so, that's bad assumption.
> 
> I assume that is due to c-make-noise-macro-regexps being a new feature
> on the master branch. The following patch fixes it for me:

Thanks.  This eliminates the error, but not the annoying question
about unsafe variables.





  reply	other threads:[~2016-05-07 17:32 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-07  7:27 bug#23476: 25.0.93; Visiting C files on master signals an error Eli Zaretskii
2016-05-07 16:43 ` Andy Moreton
2016-05-07 17:32   ` Eli Zaretskii [this message]
2016-05-07 17:50     ` Alan Mackenzie
2016-05-07 18:19       ` Eli Zaretskii
2016-05-07 18:52         ` Alan Mackenzie
2016-05-07 18:57           ` Eli Zaretskii
2016-05-07 19:30             ` Eli Zaretskii
2016-05-07 20:40               ` Alan Mackenzie
2016-05-08 15:48                 ` Eli Zaretskii
2016-05-09 11:07                   ` Alan Mackenzie
2016-05-09 16:52                     ` Eli Zaretskii
2016-05-09 18:22                       ` Alan Mackenzie
2016-05-09 19:11                         ` Eli Zaretskii
2016-05-10  3:58                           ` Glenn Morris
2016-05-10  7:51                           ` bug#23476: Slowdown in C Mode fontification [Was: bug#23476: 25.0.93; Visiting C files on master signals an error] Alan Mackenzie
2016-05-10 15:04                             ` Alan Mackenzie
2016-05-10 16:04                             ` Eli Zaretskii
2016-05-10 19:00                               ` bug#23476: Slowdown in C Mode fontification Alan Mackenzie
2016-05-09 12:01                 ` bug#23476: 25.0.93; Visiting C files on master signals an error Stefan Monnier
2016-05-07 20:10             ` Alan Mackenzie
     [not found] ` <mailman.2399.1462642391.7477.bug-gnu-emacs@gnu.org>
2016-05-09 18:34   ` Alan Mackenzie
2016-05-09 20:46 ` Óscar Fuentes
2016-05-10  2:34   ` Eli Zaretskii
2016-05-10 17:32 ` Óscar Fuentes

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=83oa8hepuj.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=23476@debbugs.gnu.org \
    --cc=andrewjmoreton@gmail.com \
    /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).