unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: define-derived-mode
Date: Mon, 09 May 2005 04:57:44 -0400	[thread overview]
Message-ID: <E1DV45A-0006fp-Hb@fencepost.gnu.org> (raw)
In-Reply-To: <200505081748.j48HmHm26026@raven.dms.auburn.edu> (message from Luc Teirlinck on Sun, 8 May 2005 12:48:17 -0500 (CDT))

    If I understood correctly, define-generic-mode only started
    constructing automatic defcustoms recently, which was an incompatible
    change.   In that case, it could easily be reversed, which would make
    the two major mode defining functions consistent in this respect.

    For define-minor-mode, the situation is more complex.  It already
    defined defcustoms in 21.3.  So here, removing them would be an
    incompatible change.  It is possible that some users already
    customized these hooks through Custom.

Such a change is no big deal.  Let's turn off generation of these
defcustoms.

  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       ` define-derived-mode Richard Stallman
2005-05-08 17:48     ` define-derived-mode Luc Teirlinck
2005-05-09  8:57       ` Richard Stallman [this message]
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=E1DV45A-0006fp-Hb@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).