From: Drew Adams <drew.adams@oracle.com>
To: Dan Espen <despen@verizon.net>, help-gnu-emacs@gnu.org
Subject: RE: force reparse of file variables
Date: Thu, 13 Aug 2015 11:23:07 -0700 (PDT) [thread overview]
Message-ID: <538f3869-f7ea-4ed3-ac45-dc40a3a283c9@default> (raw)
In-Reply-To: <mqikt3$uos$1@dont-email.me>
> > Is there a way to force (re)-load all the file variables in a buffer?
> >
> > I have a template (with yasnippet) that populates files of certain
> > types and derives some file variables (such as the 'compile-command),
> > but I need to save/open to load it.
>
> Do that lots of times. I save the file, then revert-buffer.
C-x C-v RET
IOW, `find-alternate-file' should do what you want, I think. It kills
the buffer and revisits the file.
next prev parent reply other threads:[~2015-08-13 18:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 16:59 force reparse of file variables Sam Halliday
2015-08-13 17:43 ` Dan Espen
2015-08-13 18:23 ` Drew Adams [this message]
2015-08-14 12:54 ` Sam Halliday
2015-08-14 13:14 ` Michael Heerdegen
[not found] ` <mailman.8326.1439558135.904.help-gnu-emacs@gnu.org>
2015-08-14 13:41 ` Dan Espen
2015-08-14 15:23 ` Sam Halliday
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=538f3869-f7ea-4ed3-ac45-dc40a3a283c9@default \
--to=drew.adams@oracle.com \
--cc=despen@verizon.net \
--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).