From: Chong Yidong <cyd@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: lispref/hooks.texi
Date: Sun, 26 Feb 2012 15:49:08 +0800 [thread overview]
Message-ID: <87wr7a826j.fsf@gnu.org> (raw)
In-Reply-To: <cdzkc6fjwc.fsf@fencepost.gnu.org> (Glenn Morris's message of "Sat, 25 Feb 2012 20:44:35 -0500")
Glenn Morris <rgm@gnu.org> writes:
> How about merging the general information about hooks from the start
> of hooks.texi into the section "Hooks" in modes.texi (if not there
> already), and removing hooks.texi?
The idea behind this appendix, I think, is that if someone is not sure
which hook to put a function onto, it's good to have a list of possible
hooks to use.
If we agree that that's its purpose, I think we should take out all the
hooks not related to general Emacs editing, e.g. `blink-paren-function',
`diary-*-hook', and `font-lock-beginning-of-syntax-function'. This will
also make hooks.texi easier to maintain.
> I just noticed
> Appendix G Buffer-Local Variables
> and
> Appendix H Standard Keymaps
> about which I would say much the same.
Appendix G seems pretty useless. Appendix H can be kept, but we should
remove all the mode-specific keymaps, like `apropos-mode-map' and
`c-mode-map', and just state that each mode has an associated keymap.
next prev parent reply other threads:[~2012-02-26 7:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-26 1:44 lispref/hooks.texi Glenn Morris
2012-02-26 2:11 ` lispref/hooks.texi Glenn Morris
2012-02-26 7:49 ` Chong Yidong [this message]
2012-02-26 16:05 ` lispref/hooks.texi Stefan Monnier
2012-02-26 18:42 ` lispref/hooks.texi Drew Adams
2012-02-26 16:55 ` lispref/hooks.texi Eli Zaretskii
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=87wr7a826j.fsf@gnu.org \
--to=cyd@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rgm@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).