unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jambunathan K <kjambunathan@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 13862@debbugs.gnu.org
Subject: bug#13862: 24.3.50; File local-variables error: (error "Local variables entry is missing the prefix")
Date: Mon, 04 Mar 2013 09:08:54 +0530	[thread overview]
Message-ID: <87ppzf7s1d.fsf@gmail.com> (raw)
In-Reply-To: <6jwqto10ig.fsf@fencepost.gnu.org> (Glenn Morris's message of "Sun, 03 Mar 2013 19:17:43 -0500")

Glenn Morris <rgm@gnu.org> writes:

> Adding .diff and .patch to inhibit-local-variables-regexps would avoid
> this.

,----
|  ;; Local variables:
|  ;; generated-autoload-file: "org-loaddefs.el"
| +;; coding: utf-8
|  ;; End:
`----

The question is: 

Is there are any local variables in the patch?  There isn't any.  So why
should we inhibit something that is not there.

If `diff-mode' has no comment syntax defined, then by extension, it
cannot specify file local variables.

ps: I am not sure why *.patch files are visited in diff-mode?

Jambnathan K.





  reply	other threads:[~2013-03-04  3:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-03 16:14 bug#13862: 24.3.50; File local-variables error: (error "Local variables entry is missing the prefix") Jambunathan K
2013-03-03 16:21 ` Jambunathan K
2013-03-04  0:17   ` Glenn Morris
2013-03-04  3:38     ` Jambunathan K [this message]
2013-03-04  7:38       ` Glenn Morris
2013-03-04 16:07       ` Eli Zaretskii
2013-03-04 16:47         ` Stefan Monnier
     [not found] ` <handler.13862.D13862.13623827429099.notifdone@debbugs.gnu.org>
2013-03-04  7:58   ` bug#13862: closed (Re: bug#13862: 24.3.50; File local-variables error: (error "Local variables entry is missing the prefix")) Jambunathan K
2013-03-04 14:37     ` Stefan Monnier

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=87ppzf7s1d.fsf@gmail.com \
    --to=kjambunathan@gmail.com \
    --cc=13862@debbugs.gnu.org \
    --cc=rgm@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).