Gnus development mailing list
 help / color / mirror / Atom feed
From: "Edward J. Sabol" <sabol@alderaan.gsfc.nasa.gov>
Subject: Re: DWIM fix to message.el (TAB handling)
Date: Tue, 25 Feb 1997 16:47:56 -0500	[thread overview]
Message-ID: <199702252147.QAA20816@alderaan.gsfc.nasa.gov> (raw)
In-Reply-To: <w4sp2ksk1z.fsf@loiosh.kei.com> (message from Christopher Davis on 25 Feb 1997 15:32:56 -0500)

Excerpts from mail: (25-Feb-97) DWIM fix to message.el (TAB handling) by Christopher Davis
> The following will allow "tab" in a message-mode header to
> expand mail aliases as well as completing newsgroup names. This
> makes message-mode more integrated between mail and news.

As much as I agree with the sentiment behind this, I much prefer Kai's
message-x.el package which does basically the same thing, but in a more
generic, user-configurable fashion. (See the Ding mailing list archive circa
09 Aug 1996.)

> (I don't use BBDB, so if someone wants to contribute a
> BBDB-completion routine for this, feel free. :-)

Kai's message-x.el already does this. And it's trivial to add additional tab
handlers for other headers.

> I think this is the Right Thing To Do with TAB in recipient
> headers and should go in 5.4.16.

Let's roll Kai's stuff into message.el instead.

Later,
Ed


  parent reply	other threads:[~1997-02-25 21:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-02-25 20:32 Christopher Davis
1997-02-25 21:26 ` Justin Sheehy
1997-02-25 21:47 ` Edward J. Sabol [this message]
1997-02-26 10:33 ` Kai Grossjohann
1997-02-26 15:00   ` Christopher Davis
1997-02-26 16:48     ` Edward J. Sabol
1997-02-28 23:47       ` Lars Magne Ingebrigtsen
1997-03-03  9:20         ` Robert Bihlmeyer
1997-03-06 15:44   ` Christopher Davis
1997-03-06 15:56     ` Kai Grossjohann
1997-02-28 23:46 ` Lars Magne Ingebrigtsen
1997-03-01  3:53   ` Christopher Davis
1997-03-05  8:05     ` Lars Magne Ingebrigtsen
1997-03-05 11:40       ` Per Abrahamsen
1997-03-05 15:22       ` Edward J. Sabol

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=199702252147.QAA20816@alderaan.gsfc.nasa.gov \
    --to=sabol@alderaan.gsfc.nasa.gov \
    /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).