From: "Clément Pit--Claudel" <clement.pitclaudel@live.com>
To: Tassilo Horn <tsdh@gnu.org>, Eli Zaretskii <eliz@gnu.org>
Cc: 24868@debbugs.gnu.org
Subject: bug#24868: 26.0.50; LaTeX-verbatim-macros-with-delims-local isn't taken into account
Date: Thu, 3 Nov 2016 15:06:30 -0400 [thread overview]
Message-ID: <a5093600-1609-10a6-0d99-cee21c58b116@live.com> (raw)
In-Reply-To: <87r36so1hj.fsf@gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 1158 bytes --]
On 2016-11-03 14:35, Tassilo Horn wrote:
> I guess Clement is actually reporting an AUCTeX bug and accidentally
> used `report-emacs-bug' instead of `TeX-submit-bug-report'.
Spot on :) Sorry for the mistake!
> (2) there's no hook-like thing that would be run whenever some specific
> variable is modified due to file-local or directory-local variables,
> no?
There is one :)
hack-local-variables-hook is a variable defined in ‘files.el’.
Its value is nil
This variable may be risky if used as a file-local variable.
Documentation:
Normal hook run after processing a file’s local variables specs.
Major modes can use this to examine user-specified local variables
in order to initialize other data structure based on them.
> So I guess the right way to make Clément's use-case work was to
> provide functions for modifying those variables that can be run from
> an eval: local variables block and then refresh the fontification if
> needed, right?
I think installing a hack-local-variable hook would be the way to go :)
Cheers and thanks for the quick answer!
Clément.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-11-03 19:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 16:11 bug#24868: 26.0.50; LaTeX-verbatim-macros-with-delims-local isn't taken into account Clément Pit--Claudel
2016-11-03 18:05 ` Eli Zaretskii
2016-11-03 18:35 ` Tassilo Horn
2016-11-03 19:06 ` Clément Pit--Claudel [this message]
2016-11-03 19:27 ` Tassilo Horn
2016-11-03 19:09 ` Eli Zaretskii
2016-11-03 19:26 ` Clément Pit--Claudel
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a5093600-1609-10a6-0d99-cee21c58b116@live.com \
--to=clement.pitclaudel@live.com \
--cc=24868@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=tsdh@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.