From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: define-derived-mode
Date: Mon, 09 May 2005 04:57:47 -0400 [thread overview]
Message-ID: <E1DV45D-0006gY-8A@fencepost.gnu.org> (raw)
In-Reply-To: <f7ccd24b05050810001a484d5b@mail.gmail.com> (message from Juanma Barranquero on Sun, 8 May 2005 19:00:05 +0200)
> However, I am not sure we want defcustoms for *any* mode hooks. How
> often would a user want to customize one with defcustom?
C:\...\lisp> grep -E "defcustom.*-mode-hook" *.el
add-log.el:(defcustom change-log-mode-hook nil
autorevert.el:(defcustom auto-revert-mode-hook nil
So what? The question is whether these are useful,
not whether they exist.
We have just been reminded of the reasons why customizing
these hooks is likely not to work right--in addition to the
fact that the motive to do so is probably rare.
We wrote those defcustoms because a feeling developed
that it was the right thing to use defcustom for every
variable that someone might perhaps want to customize.
But that doesn't mean we have to stick with them.
next prev parent reply other threads:[~2005-05-09 8:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-08 1:01 define-derived-mode Luc Teirlinck
2005-05-08 3:15 ` define-derived-mode Luc Teirlinck
2005-05-08 16:12 ` define-derived-mode Richard Stallman
2005-05-08 17:00 ` define-derived-mode Juanma Barranquero
2005-05-09 8:57 ` Richard Stallman [this message]
2005-05-08 17:48 ` define-derived-mode Luc Teirlinck
2005-05-09 8:57 ` define-derived-mode Richard Stallman
2005-05-09 10:13 ` define-derived-mode David Kastrup
2005-05-12 13:53 ` define-derived-mode Lute Kamstra
2005-05-17 15:58 ` define-derived-mode Lute Kamstra
2005-05-09 10:35 ` define-derived-mode Lute Kamstra
2005-05-10 0:07 ` define-derived-mode Luc Teirlinck
2005-05-10 8:47 ` define-derived-mode Lute Kamstra
2005-05-08 14:04 ` define-derived-mode 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=E1DV45D-0006gY-8A@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).