Gnus development mailing list
 help / color / mirror / Atom feed
From: "Paul D. Smith" <psmith@BayNetworks.com>
Cc: engstrom@src.honeywell.com (Eric Engstrom), ding@ifi.uio.no
Subject: Re: gnus-*-mail
Date: Tue, 26 Mar 96 00:29:45 EST	[thread overview]
Message-ID: <9603260529.AA17394@lemming.engeast> (raw)
In-Reply-To: <w8spwa0y0mh.fsf@aegir.ifi.uio.no>

%% Regarding Re: gnus-*-mail;
%% Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:

    lmi> But I should probably get in touch with the mh-e & VM people to
    lmi> see whether a merger might be worked out...

Indeed; I'd love to have vm-mail worked into this.  Note that VM is
frame-aware, though, which GNUS doesn't seem to be so far.  I think
that's important (I'd love to have gnus-post-other-frame, for example).

    >> While you are at it, I can provide a quick hack to allow
    >> completion of addresses on From:, CC:, etc, lines; it gets
    >> completion values from a variety of sources including .mailrc,
    >> /etc/aliases and YP/NIS aliases.

    lmi> That sounds interesting.  There is already a mailalias.el file,
    lmi> but I don't quite know what that one offers...

Please make this kind of thing configurable; our NIS aliases database is
_HUGE_, and I don't want to complete on it in any way.  That's what BBDB
is for!  Now _there's_ a worthwhile package to make sure message.el
works with.

Also, Kyle Jones, Barry Warsaw, and others came up with a set of rules
that Emacs messaging systems should obey, to allow citing engines like
supercite to work.  I don't know how much of that is interesting for
message.el but it should be taken into account.

And finally, I much prefer mailabbrev.el to mailalias.el, so if you're
looking for that kind of thing, there's my vote--plus my mabbrev-menu
package creates a menu bar menu for mailabbrev aliases :)


  reply	other threads:[~1996-03-26  5:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-03-22 11:19 gnus-*-mail d. hall
1996-03-22 18:48 ` gnus-*-mail Lars Magne Ingebrigtsen
1996-03-22 19:33   ` gnus-*-mail Paul D. Smith
1996-03-22 21:46     ` gnus-*-mail d. hall
1996-03-22 21:55     ` gnus-*-mail Lars Magne Ingebrigtsen
1996-03-24 21:10   ` gnus-*-mail Eric Engstrom
1996-03-25  6:16     ` gnus-*-mail Per Abrahamsen
1996-03-26  3:49     ` gnus-*-mail Lars Magne Ingebrigtsen
1996-03-26  5:29       ` Paul D. Smith [this message]
1996-04-18 13:30         ` gnus-*-mail Lars Magne Ingebrigtsen
1996-03-27 17:13       ` gnus-*-mail Scott Blachowicz
1996-03-27 19:43     ` gnus-*-mail David C Worenklein

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=9603260529.AA17394@lemming.engeast \
    --to=psmith@baynetworks.com \
    --cc=ding@ifi.uio.no \
    --cc=engstrom@src.honeywell.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.
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 NNTP newsgroup(s).