From: Kevin Rodgers <kevin.d.rodgers@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Local variables not being defined
Date: Wed, 31 Jan 2007 22:17:53 -0700 [thread overview]
Message-ID: <eprt61$7fg$1@sea.gmane.org> (raw)
In-Reply-To: <45C08E00.5060705@gmx.at>
martin rudalics wrote:
> > 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:
>
> I don't know about the missing colon, but
>
> -- User Option: case-fold-search
> This buffer-local variable determines whether searches should
> ignore case. If the variable is `nil' they do not ignore case;
> otherwise they do ignore case.
>
> hence
>
> > (when (let ((case-fold-search t))
> > (search-forward "Local Variables:" nil t))
> > (skip-chars-forward " \t")
>
> does not look for the exact string.
Oops, I failed to actually read the code and just assumed it bound
case-fold-search to nil -- after all, the Emacs manual always
capitalizes both words.
So why does hack-local-variables bind case-fold-search to t? Is that
not a bug?
--
Kevin Rodgers
Denver, Colorado, USA
next prev parent reply other threads:[~2007-02-01 5:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 12:39 Local variables not being defined martin rudalics
2007-02-01 5:17 ` Kevin Rodgers [this message]
[not found] <mailman.3574.1169739033.2155.help-gnu-emacs@gnu.org>
2007-01-25 16:20 ` 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
-- 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='eprt61$7fg$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.
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).