From: Kevin Rodgers <kevinr@ihs.com>
Subject: Re: Reparsing local variables without reopening file?
Date: Tue, 24 Sep 2002 14:22:05 -0600 [thread overview]
Message-ID: <3D90C96D.4090100@ihs.com> (raw)
In-Reply-To: xcvheghsyyo.fsf@hurricane.OCF.Berkeley.EDU
Thomas F. Burdick wrote:
> Come to think of it, that would be a nice thing to have as a command,
> wouldn't it? But hack-local-variables is the function that gets
> called when you find-file a file, so you can just put this in your
> .emacs:
>
> (defun my-reparse-local-variables ()
> (interactive)
> (hack-local-variables))
>
> (global-set-key ... #'my-reparse-local-varaibles)
Or you can advise the original definition and bind a key to that (or
call it via M-x), instead of creating a new function:
(defadvice hack-local-variables (before interactive activate)
"Provide an `interactive' specification."
(interactive))
--
<a href="mailto:<kevinr@ihs.com>">Kevin Rodgers</a>
next prev parent reply other threads:[~2002-09-24 20:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-21 19:13 Reparsing local variables without reopening file? Ole Laursen
2002-09-21 22:27 ` Michael Slass
2002-09-22 17:42 ` Thomas F. Burdick
2002-09-24 20:22 ` Kevin Rodgers [this message]
2002-09-23 12:29 ` Peter Boettcher
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=3D90C96D.4090100@ihs.com \
--to=kevinr@ihs.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).