unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 23476@debbugs.gnu.org
Subject: bug#23476: 25.0.93; Visiting C files on master signals an error
Date: Mon, 9 May 2016 18:22:06 +0000	[thread overview]
Message-ID: <20160509182206.GC5316@acm.fritz.box> (raw)
In-Reply-To: <83shxrcgxz.fsf@gnu.org>

Hello, Eli.

On Mon, May 09, 2016 at 07:52:08PM +0300, Eli Zaretskii wrote:
> > Date: Mon, 9 May 2016 11:07:13 +0000
> > Cc: 23476@debbugs.gnu.org
> > From: Alan Mackenzie <acm@muc.de>

[ .... ]

> > Right.  I've amended C(etc.) Mode to use the new :after-hook parameter
> > to define-derived-mode which I committed yesterday.  The eval form which
> > used to be in .dir-locals.el is now run by C Mode after the mode hooks
> > (and file/dir local variables stuff) have been done.

> Thanks.

[ .... ]

> > One way to get round this would be to add the safe-local-variable
> > stuff into emacs-25, but nobody wants to change emacs-25 at this
> > late stage.

> Adding a variable that is not used for anything but declaring its safe
> values should be OK, I think.

> > Just how bad would it be to get the question about unsafe local
> > variables when visiting master C files from emacs-25 emacs -Q?

> It's better, but still an annoyance.  And if the solution in non-Q
> sessions is to accept the variable as safe anyway, then adding the
> variable instead for the same purpose is not different, and should be
> "safe" (pun intended ;-).

OK, Done.  (Full patch in master, minimal patch in emacs-25).

-- 
Alan Mackenzie (Nuremberg, Germany).





  reply	other threads:[~2016-05-09 18:22 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
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 [this message]
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=20160509182206.GC5316@acm.fritz.box \
    --to=acm@muc.de \
    --cc=23476@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).