From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: hack-local-variables
Date: Sun, 08 May 2005 18:45:53 -0400 [thread overview]
Message-ID: <E1DUuX3-0001oe-0e@fencepost.gnu.org> (raw)
In-Reply-To: <200505072232.j47MWS524175@raven.dms.auburn.edu> (message from Luc Teirlinck on Sat, 7 May 2005 17:32:28 -0500 (CDT))
The behavior of `hack-local-variables' has recently been changed.
I don't see any recent change. What change do you mean?
The patch below updates the Elisp manual. I can
install if desired.
Please do.
Since this is an incompatible change, should it also be mentioned in
the NEWS?
I think mentioning such minor details would only add clutter; it would
get in the way of reading the changes people want to know about.
So please don't.
next prev parent reply other threads:[~2005-05-08 22:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-07 22:32 hack-local-variables Luc Teirlinck
2005-05-08 22:45 ` Richard Stallman [this message]
2005-05-09 2:36 ` hack-local-variables Luc Teirlinck
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=E1DUuX3-0001oe-0e@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).