unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Bill Wohler <wohler@newt.com>
Cc: mh-e-devel@lists.sourceforge.net
Subject: Re: Customization group aliases
Date: Fri, 27 May 2005 11:12:16 -0700	[thread overview]
Message-ID: <25671.1117217536@olgas.newt.com> (raw)
In-Reply-To: Richard Stallman's message of Thu, 26 May 2005 10:53:53 EDT. <E1DbJk9-0008Gk-Ie@fencepost.gnu.org>

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

  reply	other threads:[~2005-05-27 18:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87vf56517m.fsf@olgas.newt.com>
2005-05-26 14:53 ` Customization group aliases Richard Stallman
2005-05-27 18:12   ` Bill Wohler [this message]
2005-05-25 23:34 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=25671.1117217536@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).