From: Kevin Rodgers <kevin.d.rodgers@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Local variables not being defined
Date: Tue, 30 Jan 2007 22:34:30 -0700 [thread overview]
Message-ID: <epp9os$6nq$1@sea.gmane.org> (raw)
In-Reply-To: <45B9E36A.3040309@speakeasy.net>
ken wrote:
>
> On 01/25/2007 05:22 PM somebody named Harald Hanche-Olsen wrote:
>> + ken <gebser@speakeasy.net>:
>>
>> ....
>>
>> 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?
>
> Thanks, Harald. You have very good eyes to see across continent and
> ocean. I titled my test document so:
>
> <h1 align=center>Testing the Use of Local Variables in....
>
> Replacing a SPACE with " " made the errors cease. (I was frankly
> surprised that the (uppercase) 'V' and absence of the colon after
> "Variables" didn't distinguish this text enough from the intended
> instance. Perhaps a later version has/will.)
hack-local-variables only goes back to the last newline or formfeed
character, to a maximum of 3000 characters. So the recommended practice
is to precede the local variables section with a page break (control-L,
usually on a line by itself).
And hack-local-variables does search for the exact "Local Variables:"
string, so should not have found an occurrence with a lower case `v' and
missing colon:
(when (let ((case-fold-search t))
(search-forward "Local Variables:" nil t))
(skip-chars-forward " \t")
...
So perhaps you've got a locally hacked version of hack-local-variables...
> So, another dark obscure code corner illuminated, good karma created.
Let's hope!
--
Kevin Rodgers
Denver, Colorado, USA
next prev parent reply other threads:[~2007-01-31 5:34 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
2007-01-26 11:18 ` ken
2007-01-31 5:34 ` Kevin Rodgers [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='epp9os$6nq$1@sea.gmane.org' \
--to=kevin.d.rodgers@gmail.com \
--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.
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.