Reparsing local variables without reopening file?

Reparsing local variables without reopening file?

[Ole Laursen]

Hi

I was changing a local variable for a test example when it occurred to
me that I didn't know how to make Emacs reparse them. For example:

  // Local Variables: ***
  // compile-command: "g++ test.cpp -o test -O3" ***
  // End: ***

Now, one can save and kill the buffer and refind the file (or perhaps
even do a M-x revert-buffer); however, this seems silly. M-x apropos
gives hack-local-variables. But that is a function? What do the gurus
do? Or should hack-local-variables be a command (perhaps with a
somewhat more descriptive name :-)? Typing M-: (hack-local-variables)
is a little laborious.

-- 
Ole Laursen
http://sunsite.dk/olau/

Re: Reparsing local variables without reopening file?

[Michael Slass]

Ole Laursen <olau@hardworking.dk> writes:

>Hi
>
>I was changing a local variable for a test example when it occurred to
>me that I didn't know how to make Emacs reparse them. For example:
>
>  // Local Variables: ***
>  // compile-command: "g++ test.cpp -o test -O3" ***
>  // End: ***
>
>Now, one can save and kill the buffer and refind the file (or perhaps
>even do a M-x revert-buffer); however, this seems silly. M-x apropos
>gives hack-local-variables. But that is a function? What do the gurus
>do? Or should hack-local-variables be a command (perhaps with a
>somewhat more descriptive name :-)? Typing M-: (hack-local-variables)
>is a little laborious.

A faster way to do that is with find-alternate-file (usually bound to
C-x C-v) and then accept the default which will be the file you're
currently visiting.  This will re-load the file from disk, re-start
the appropriate mode, and eval the local variables.

That doesn't address your point of any other way to do it, but makes
your way easier to do.

BOL

-- 
Mike Slass

Re: Reparsing local variables without reopening file?

[Thomas F. Burdick]

Ole Laursen <olau@hardworking.dk> writes:

> Hi
> 
> I was changing a local variable for a test example when it occurred to
> me that I didn't know how to make Emacs reparse them. For example:
> 
>   // Local Variables: ***
>   // compile-command: "g++ test.cpp -o test -O3" ***
>   // End: ***
> 
> Now, one can save and kill the buffer and refind the file (or perhaps
> even do a M-x revert-buffer); however, this seems silly. M-x apropos
> gives hack-local-variables. But that is a function? What do the gurus
> do? Or should hack-local-variables be a command (perhaps with a
> somewhat more descriptive name :-)? Typing M-: (hack-local-variables)
> is a little laborious.

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)

-- 
           /|_     .-----------------------.                        
         ,'  .\  / | No to Imperialist war |                        
     ,--'    _,'   | Wage class war!       |                        
    /       /      `-----------------------'                        
   (   -.  |                               
   |     ) |                               
  (`-.  '--.)                              
   `. )----'                               

Re: Reparsing local variables without reopening file?

[Kevin Rodgers]

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:&lt;kevinr&#64;ihs.com&gt;">Kevin Rodgers</a>

Re: Reparsing local variables without reopening file?

[Peter Boettcher]

On 21 Sep 2002, olau@hardworking.dk wrote:
> Hi
> 
> I was changing a local variable for a test example when it occurred
> to me that I didn't know how to make Emacs reparse them. For
> example:
> 
>   // Local Variables: ***
>   // compile-command: "g++ test.cpp -o test -O3" ***
>   // End: ***
> 
> Now, one can save and kill the buffer and refind the file (or
> perhaps even do a M-x revert-buffer); however, this seems silly. M-x
> apropos gives hack-local-variables. But that is a function? What do
> the gurus do? Or should hack-local-variables be a command (perhaps
> with a somewhat more descriptive name :-)? Typing M-:
> (hack-local-variables) is a little laborious.

I use M-x normal-mode for this kind of thing.  I bind it to C-c n.

-- 
Peter Boettcher
MIT Lincoln Laboratory
boettcher@ll.mit.edu