From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: custom function to modify Gcc
Date: Wed, 15 Aug 2001 12:04:38 +0200 [thread overview]
Message-ID: <vafsnetprk9.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m3zo924ck0.fsf@onyx.nimbus.northernlight.com> (Ted Zlatanov's message of "Tue, 14 Aug 2001 16:22:07 -0400")
Ted Zlatanov <tzz@northernlight.com> writes:
> (setq header-action-list
> '(("Subject:"
> (".*status report.*"
> (lambda()
> (save-excursion
> (mail-position-on-field "Gcc")
> (insert ",status") ; there already is an archive entry here
> ))))))
I don't know anything about header-action, but the above code looks
okay, especially the mail-position-on-field part.
But shouldn't you include the server name in the group name, as in
"nnfolder:status" rather than just "status"?
kai
--
~/.signature: No such file or directory
prev parent reply other threads:[~2001-08-15 10:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-14 18:23 Ted Zlatanov
2001-08-14 19:08 ` Paul Jarc
2001-08-14 20:03 ` Kai Großjohann
2001-08-14 20:22 ` Ted Zlatanov
2001-08-15 10:04 ` 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=vafsnetprk9.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=ding@gnus.org \
/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).