all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: 13862@debbugs.gnu.org
Subject: bug#13862: closed (Re: bug#13862: 24.3.50; File local-variables error: (error "Local variables entry is missing the prefix"))
Date: Mon, 04 Mar 2013 09:37:42 -0500	[thread overview]
Message-ID: <jwvppzfcjud.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <8738wbfver.fsf@gmail.com> (Jambunathan K.'s message of "Mon, 04 Mar 2013 13:28:52 +0530")

>>> Is there are any local variables in the patch?  There isn't any.  So why
>>> should we inhibit something that is not there.
>> Inhibit to prevent a false detection, exactly as in this case.
>>> If `diff-mode' has no comment syntax defined, then by extension, it
>>> cannot specify file local variables.
>> Err, you can specify file local variables without a prefix. Eg
>> etc/NEWS.
> Seems to me that it is worth re-visiting the above decision.  Closing
> the bug will only suppress further arguments surrounding this bug.

I think we should start by turning the error into a warning.


        Stefan





      reply	other threads:[~2013-03-04 14:37 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
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 [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvppzfcjud.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=13862@debbugs.gnu.org \
    --cc=kjambunathan@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.