Gnus development mailing list
 help / color / mirror / Atom feed
From: engstrom@src.honeywell.com (Eric Engstrom)
Cc: ding@ifi.uio.no
Subject: Re: gnus-*-mail
Date: Sun, 24 Mar 96 15:10:31 CST	[thread overview]
Message-ID: <9603242110.AA15446@riffraff.src.honeywell.com> (raw)
In-Reply-To: larsi@ifi.uio.no's message of 22 Mar 1996 19:48:22 +0100

>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:
LMI> However, I've suggested to RMS that I write a new message.el to
LMI> combine gnus-msg.el, sendmail.el, rnewspost.el (etc) into just one
LMI> message composition mode.  He seems positive, so I'll probably be
LMI> doing that in the not-too-distant future. 

Not to make the job any more difficult, but how about working with the mh-e
folks and merge in the stuff from mh-send (mh-comp.el).

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.

eric
--
Eric Engstrom, Research Scientist, SW Eng. Methods, Honeywell/HTC, Mpls, MN USA
engstrom@htc.honeywell.com -- MIME/PGP mail accepted -- finger -l for more info
 <baroque \b*-'ro-k\ adj [F,fr. barocco]: of, relating to, or having no monet>


  parent reply	other threads:[~1996-03-24 21:10 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   ` Eric Engstrom [this message]
1996-03-25  6:16     ` gnus-*-mail Per Abrahamsen
1996-03-26  3:49     ` gnus-*-mail Lars Magne Ingebrigtsen
1996-03-26  5:29       ` gnus-*-mail Paul D. Smith
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=9603242110.AA15446@riffraff.src.honeywell.com \
    --to=engstrom@src.honeywell.com \
    --cc=ding@ifi.uio.no \
    /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).