From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: Force Reread of "local variables:"
Date: Mon, 02 Feb 2004 16:08:57 -0700 [thread overview]
Message-ID: <401ED889.7030802@yahoo.com> (raw)
In-Reply-To: 87wu7539ea.fsf@ID-87814.user.dfncis.de
Oliver Scholz wrote:
> If your auto-mode detection is set up correctly and if you don't have
> important buffer-local variables other than those in the “Local
> Variables” section, you can just do M-x normal-mode RET.
>
> I mention these two “ifs” above, because as far as buffer variables
> are concerned this has basically the same effect as killing the buffer
> and re-visiting it.
So why not just type `C-x C-v RET'?
--
Kevin Rodgers
next prev parent reply other threads:[~2004-02-02 23:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-01 5:01 Force Reread of "local variables:" Tennis Smith
2004-02-01 5:50 ` Eli Zaretskii
2004-02-02 13:23 ` Oliver Scholz
2004-02-02 23:08 ` Kevin Rodgers [this message]
2004-02-03 4:29 ` Oliver Scholz
2004-02-03 17:57 ` Kevin Rodgers
2004-02-03 10:37 ` Reiner Steib
2004-02-02 15:06 ` Joakim Hove
2004-02-03 0:18 ` Tennis Smith
2004-02-03 9:14 ` Joakim Hove
2004-02-03 19:11 ` Reiner Steib
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=401ED889.7030802@yahoo.com \
--to=ihs_4664@yahoo.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.
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).