From: Harald Hanche-Olsen <hanche@math.ntnu.no>
To: help-gnu-emacs@gnu.org
Subject: Re: Local variables not being defined
Date: Thu, 25 Jan 2007 23:22:54 +0100 [thread overview]
Message-ID: <pco3b5ylpa9.fsf@shuttle.math.ntnu.no> (raw)
In-Reply-To: mailman.3599.1169761553.2155.help-gnu-emacs@gnu.org
+ ken <gebser@speakeasy.net>:
| On 01/25/2007 03:25 PM somebody named Harald Hanche-Olsen wrote:
|> + ken <gebser@speakeasy.net>:
|>
|> | File local-variables error: (error "Local variables entry is missing the
|> | prefix")
|> |
|> | So what does this error message mean and/or what should I do about it?
|>
|> See the info file about file variables: Every line of the Variables
|> section must have the exact same prefix, which may be empty. This
|> appears to be the case with your example. Or did some lines have
|> initial spaces or tabs that your news posting software suppressed?
|> If so, get rid of them.
|>
|
| That can't be the problem
You asked what the error message means, and that is what it means.
| as the "prefix" is and has always been the same for all lines--
| nothing at all. I.e., all lines start to the far left... in the
| very first column.
Then what happens shouldn't happen, and I am left powerless to suggest
other explanations.
| Again:
Yup, I saw that the first time. (I suggested leading white space
because I have often seen news posting software suppressing white
space, and then I wouldn't see it obviously. I'll take your word for
it not being there.) And it works for me: I copied your local
variables section verbatim to an HTML file, saved, closed the buffer
and reloaded, and the variables get the prescribed values, no problem.
I am looking at the code now (the function in question is called
hack-local-variables, and it is found in files.el), and there should
be no way you are going to see that message unless there is something
in front of the string "Local Variables:" on the line.
Oh, wait, one more wild guess. hack-local-variables goes 3000
characters back from the end of the file and searches forward for
"Local Variables:". Don't tell me your HTML file contains another
instance of that phrase?
--
* Harald Hanche-Olsen <URL:http://www.math.ntnu.no/~hanche/>
- It is undesirable to believe a proposition
when there is no ground whatsoever for supposing it is true.
-- Bertrand Russell
next prev parent reply other threads:[~2007-01-25 22:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3574.1169739033.2155.help-gnu-emacs@gnu.org>
2007-01-25 16:20 ` Local variables not being defined Harald Hanche-Olsen
2007-01-25 19:44 ` ken
[not found] ` <mailman.3592.1169754294.2155.help-gnu-emacs@gnu.org>
2007-01-25 20:25 ` Harald Hanche-Olsen
2007-01-25 21:45 ` ken
2007-01-25 22:08 ` ken
[not found] ` <mailman.3603.1169762957.2155.help-gnu-emacs@gnu.org>
2007-01-25 22:25 ` Harald Hanche-Olsen
[not found] ` <mailman.3599.1169761553.2155.help-gnu-emacs@gnu.org>
2007-01-25 22:22 ` Harald Hanche-Olsen [this message]
2007-01-26 11:18 ` ken
2007-01-31 5:34 ` Kevin Rodgers
2007-01-31 12:39 martin rudalics
2007-02-01 5:17 ` Kevin Rodgers
-- strict thread matches above, loose matches on Subject: below --
2007-01-25 15:29 ken
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=pco3b5ylpa9.fsf@shuttle.math.ntnu.no \
--to=hanche@math.ntnu.no \
--cc=help-gnu-emacs@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.
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).