From: Richard Stallman <rms@gnu.org>
Cc: teirllm@dms.auburn.edu, emacs-devel@gnu.org
Subject: Re: define-derived-mode
Date: Sun, 08 May 2005 12:12:27 -0400 [thread overview]
Message-ID: <E1DUoOJ-0003Ef-UH@fencepost.gnu.org> (raw)
In-Reply-To: <200505080315.j483F2l24405@raven.dms.auburn.edu> (message from Luc Teirlinck on Sat, 7 May 2005 22:15:02 -0500 (CDT))
If one would make it construct defcustoms, then maybe that should only
happen if the :group keyword is given, so it would not get into the
same default group problems as `define-{minor,generic}-mode'.
I don't follow the logic of this argument. Whatever group is right
for the move variable, isn't that right for the hook variable too?
However, I am not sure we want defcustoms for *any* mode hooks. How
often would a user want to customize one with defcustom? It seems to
me that defcustoms for mode hooks are mostly useless clutter.
What argument is there that they are useful and worth their cost?
next prev parent reply other threads:[~2005-05-08 16:12 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 ` Richard Stallman [this message]
2005-05-08 17:00 ` define-derived-mode Juanma Barranquero
2005-05-09 8:57 ` define-derived-mode Richard Stallman
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=E1DUoOJ-0003Ef-UH@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=teirllm@dms.auburn.edu \
/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).