From: CHENG Gao <chenggao@gmail.com>
Subject: Re: Is it intended to change hook names to follow coding conventions?
Date: Wed, 24 Nov 2004 23:34:06 +0800 [thread overview]
Message-ID: <d5y36z2p.fsf@gmail.com> (raw)
In-Reply-To: E1CWmro-0001iE-Is@fencepost.gnu.org
In files.el,
`write-file-hooks is defined as alias for `write-file-functions.
`find-file-not-found-hooks is defined as alias for `find-file-not-found-functions.
`find-file-hooks is defined as alias for `find-file-hook.
They are all explicitly marked as obselete.
I think at least it's safe to fix all occurences of them to use new
convention-conformant names.
Just my 0.02 RMB Yuan.
--
酌贪泉而觉爽，处涸辙以犹欢
next prev parent reply other threads:[~2004-11-24 15:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 17:15 Is it intended to change hook names to follow coding conventions? CHENG Gao
2004-11-22 20:57 ` Thien-Thi Nguyen
2004-11-24 2:26 ` Richard Stallman
2004-11-24 15:34 ` CHENG Gao [this message]
2004-11-26 17:21 ` Richard Stallman
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=d5y36z2p.fsf@gmail.com \
--to=chenggao@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).