Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: gnus-post-method and message-expand-group
Date: 27 Aug 1999 23:42:44 +0200	[thread overview]
Message-ID: <vafbtbsaoiz.fsf@petty.cs.uni-dortmund.de> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "27 Aug 1999 23:29:22 +0200"

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Well, how about if we incorporate message-x in Gnus, remove
> message-expand-group and add instead an alist of abbrev expansion
> thingies.  Like:
> 
> (defvar message-header-expansion-functions
>    ("^\\(Newsgroups\\|Followup-To\\|Posted-To\\|Gcc\\):" message-x-expand)
>    ("Some-other: " other-expanding-function))
> 
> If none of these match, then we call `tab-to-tab-stop', which will do
> the abbrev abbrev expansion.
> 
> Whaddayouthink?

Well, message-x.el pretty much tries what you are suggesting here, I
think.  There's an alist which gives the expansion function for each
header.  For Newsgroups and Gcc and Followup-to, message-expand-group
is called.

message-x doesn't grok regexes in the alist, though.

And we still need a second function similar to message-expand-group
which looks at gnus-post-method.

I'll try to do what you are suggesting, and I'll post the new
message-x when I'm done.

kai
-- 
I like BOTH kinds of music.


      reply	other threads:[~1999-08-27 21:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-20 14:44 Kai Großjohann
1999-08-27 20:23 ` Lars Magne Ingebrigtsen
1999-08-27 20:52   ` Kai Großjohann
1999-08-27 21:29     ` Lars Magne Ingebrigtsen
1999-08-27 21:42       ` Kai Großjohann [this message]

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=vafbtbsaoiz.fsf@petty.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    /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).