all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: <emacs-pretest-bug@gnu.org>
Subject: bug#3566: 23.0.94; explain why not to use group defined by define-minor-mode
Date: Sun, 14 Jun 2009 13:23:10 -0700	[thread overview]
Message-ID: <4276C1AF57E24DE89998752CA7F77EE1@us.oracle.com> (raw)

In the Elisp manual and in the doc string for define-minor-mode, we
are told not to use the custom group that is automatically defined for
the mode variable, unless we have explicitly used defgroup to define
the group.
 
Why? Please provide some explanation.
 
If you use `define-globalized-minor-mode', then the generated group
(with the name of the _local_ minor mode) is recognized by
`customize-group', and the mode variable for the global mode is
recognized by `customize-variable'.
 
Why is it inadvisable to use the same generated group for other
defcustoms without explicitly defining the group? What negative
consequences arise if that is attempted? Please explain in the doc.
 
The Elisp manual, node Defining Minor Modes, seems to refer you to
node `Group Definitions' for the explanation of this warning, but
there is no such explanation there:
 
"*Warning:* don't use this default group name unless you have
written a `defgroup' to define that group properly. *Not
Group Definitions."
 

In GNU Emacs 23.0.94.1 (i386-mingw-nt5.1.2600)
 of 2009-05-24 on SOFT-MJASON
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4)'
 






             reply	other threads:[~2009-06-14 20:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-14 20:23 Drew Adams [this message]
2011-07-12 14:07 ` bug#3566: 23.0.94; explain why not to use group defined by define-minor-mode Lars Magne Ingebrigtsen
2016-04-27 20:02 ` Lars Ingebrigtsen
2016-04-27 20:04   ` Lars Ingebrigtsen

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4276C1AF57E24DE89998752CA7F77EE1@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=3566@emacsbugs.donarmstrong.com \
    --cc=emacs-pretest-bug@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.