Customization group aliases

Customization group aliases

[Bill Wohler]

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.

Re: Customization group aliases

[Richard Stallman]

    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 ;-).

Why don't you want this group to appear under the group `mail'?
That would seem natural to me, for all the groups used for mh-e.

Perhas you're saying that the mh-e group is intended as an alias for
the mh group.  Is that what you really want?  We could arrange some way
of doing that.



-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005

Re: Customization group aliases

[Bill Wohler]

Richard Stallman <rms@gnu.org> wrote:

> Perhas you're saying that the mh-e group is intended as an alias for
> the mh group.  Is that what you really want?  We could arrange some way
> of doing that.

That's correct. We would not want both "mh" and "mh-e" to appear in the
"mail" group.

However, I have not heard any reason why we shouldn't just rename the
"mh" group to "mh-e" and drop the alias so I've done that. At least with
completion, someone who enters just "mh" can discover that the group is
actually called "mh-e". This is not true in reverse which is why the
alias was created.

Since our next MH-E release is to be a major one, we can afford to make
such a change.

If a defgroupalias function is created, then we can use it to create a
"mh" alias. 

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


-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005