unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Howard Melman <hmelman@gmail.com>
Cc: 45864@debbugs.gnu.org
Subject: bug#45864: 27.1; hack-local-variables-hook is not documented in Emacs Manual
Date: Tue, 19 Jan 2021 07:22:55 +0100	[thread overview]
Message-ID: <875z3to37k.fsf@gnus.org> (raw)
In-Reply-To: <62F9C4EE-B85D-4348-BAF1-3358CF49193C@gmail.com> (Howard Melman's message of "Thu, 14 Jan 2021 10:43:48 -0500")

Howard Melman <hmelman@gmail.com> writes:

> Today I learned about the hack-local-variables-hook which
> allows me to correct these.  I'm surprised that it and
> before-hack-local-variables-hook are not documented in the
> Emacs Manual but are only mentioned in the Elisp Reference
> Manual.  Unless I'm misunderstanding something they're meant
> for users and not just for elisp programmers so they should
> be in the Emacs Manual.

The doc string of the former variable says:

----
Major modes can use this to examine user-specified local variables
in order to initialize other data structure based on them.
----

So they are meant for people implementing major modes, which is why
they're in the lispref manual, and not the Emacs manual.  (Users can use
them, too, but that's not really their purpose.)

So I think it makes sense to keep the documentation as is, and I'm
closing this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2021-01-19  6:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-14 15:43 bug#45864: 27.1; hack-local-variables-hook is not documented in Emacs Manual Howard Melman
2021-01-19  6:22 ` Lars Ingebrigtsen [this message]
     [not found]   ` <A6C93D80-90E0-4F4C-96AD-33953BE52EEE@gmail.com>
2021-01-19 13:19     ` Howard Melman
2021-01-19 15:47       ` Lars Ingebrigtsen

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=875z3to37k.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=45864@debbugs.gnu.org \
    --cc=hmelman@gmail.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.
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).