unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 3566@debbugs.gnu.org
Subject: bug#3566: 23.0.94; explain why not to use group defined by define-minor-mode
Date: Tue, 12 Jul 2011 16:07:41 +0200	[thread overview]
Message-ID: <m3y603mw2a.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <4276C1AF57E24DE89998752CA7F77EE1@us.oracle.com> (Drew Adams's message of "Sun, 14 Jun 2009 13:23:10 -0700")

"Drew Adams" <drew.adams@oracle.com> writes:

> 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."

Yes, this seems rather puzzling.  Anybody know the reason?

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/





  reply	other threads:[~2011-07-12 14:07 UTC|newest]

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

  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=m3y603mw2a.fsf@quimbies.gnus.org \
    --to=larsi@gnus.org \
    --cc=3566@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    /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).