From: Bill Wohler <wohler@newt.com>
Cc: mh-e-devel@lists.sourceforge.net
Subject: Customization group aliases
Date: Wed, 25 May 2005 16:34:53 -0700 [thread overview]
Message-ID: <87vf56517m.fsf__28465.7126213007$1117064800$gmane$org@olgas.newt.com> (raw)
I'm now getting the following warning when compiling MH-E:
mh-customize.el:111:1:Warning: defgroup for `mh-e' fails to specify
containing group
Here's the code:
(defgroup mh nil
"Emacs interface to the MH mail system.
MH is the Rand Mail Handler. Other implementations include nmh and GNU
mailutils."
:link '(custom-manual "(mh-e)Top")
:group 'mail)
(defgroup mh-e '((mh custom-group)) ; Sort of an alias for 'mh group
"Emacs interface to the MH mail system.
MH is the Rand Mail Handler. Other implementations include nmh and GNU
mailutils."
:link '(custom-manual "(mh-e)Top"))
The mh-e group only exists to point a user in the right direction if
the user happens to explicitly run "M-x customize-group mh-e RET"
which is a reasonable expectation given the name of the package ;-).
As such, I do not want this group to appear in any group. Is there a
way around this?
I also forget why we named the main group "mh" and not "mh-e". I'm
thinking of simply dropping the second group and just having a single
"mh-e" group which is a reasonable expectation given the name of the
package ;-). If no one can remember the good reason why we did this or
can think of a good reason why we do this, I'll make it so.
--
Bill Wohler <wohler@newt.com> http://www.newt.com/wohler/ GnuPG ID:610BD9AD
Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian!
If you're passed on the right, you're in the wrong lane.
next reply other threads:[~2005-05-25 23:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-25 23:34 Bill Wohler [this message]
[not found] <87vf56517m.fsf@olgas.newt.com>
2005-05-26 14:53 ` Customization group aliases Richard Stallman
2005-05-27 18:12 ` Bill Wohler
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='87vf56517m.fsf__28465.7126213007$1117064800$gmane$org@olgas.newt.com' \
--to=wohler@newt.com \
--cc=mh-e-devel@lists.sourceforge.net \
/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).