unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thien-Thi Nguyen <ttn@glug.org>
Cc: emacs-devel@gnu.org
Subject: Re: Is it intended to change hook names to follow coding conventions?
Date: 22 Nov 2004 15:57:36 -0500	[thread overview]
Message-ID: <jkvfbxlhz3.fsf@glug.org> (raw)
In-Reply-To: CHENG Gao's message of "Tue, 23 Nov 2004 01:15:01 +0800"

CHENG Gao <chenggao@gmail.com> writes:

   wanna know if it's intended to change these names to following
   this convention for next release

each change has to be considered on a case-by-case basis, w/
awareness of historical context.  for example, things that have a
lot of "area under the curve" (integrating usage over time) are
probably not good candidates for capricious change, if you wish to
save time later for hacking instead of for handling bug reports.
however, even for these kinds of things, there may be indeed be
circumstances where a hard break w/ the past accompanied by an
upward compatable alternative is worth the temporary pain.

intent is foreground, but you want to paint a nice scene, which
includes both foreground and background.  finding the background
of things is not an unpleasant way to hone your craft.

thi

  reply	other threads:[~2004-11-22 20:57 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 [this message]
2004-11-24  2:26 ` Richard Stallman
2004-11-24 15:34   ` CHENG Gao
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=jkvfbxlhz3.fsf@glug.org \
    --to=ttn@glug.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).