From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: Alex Schroeder <alex@gnu.org>, ding@gnus.org
Subject: Re: Question about mail archive
Date: 08 Apr 2001 22:23:44 +0200 [thread overview]
Message-ID: <vafbsq7i1in.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m33dbj88ty.fsf@reason.gnu-hamburg> ("Georg C. F. Greve"'s message of "08 Apr 2001 21:55:53 +0200")
On 08 Apr 2001, Georg C. F. Greve wrote:
> || On 08 Apr 2001 20:36:36 +0200
> || Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) wrote:
>
> kg> Hm. When a message comes in and you have processed it, do you
> kg> want to move or to copy it to the archive group? Anyway, maybe
> kg> a simple keybinding that you can use rather than `d' would be
> kg> sufficient? A command which marks the article as read and then
> kg> does gnus-summary-move-article to the right group?
>
> Yeah, this would probably sufficient if it prompted me with a
> reasonable name by default... maybe passing something like
>
> (setq gnus-processed-message-archive-group
> '(concat "recv." (format-time-string
> "%Y-%m" (current-time))))
>
> as the default name for the group to move to?
(gnus-summary-move-article 1 (format-time-string "recv.%Y-%m"))
Try to eval this expression using M-: on a msg. Does it move the msg
to the right group?
kai
--
Be indiscrete. Do it continuously.
next prev parent reply other threads:[~2001-04-08 20:23 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-07 11:48 Georg C. F. Greve
2001-04-07 14:54 ` Kai Großjohann
2001-04-07 15:04 ` Georg C. F. Greve
2001-04-07 15:30 ` Kai Großjohann
2001-04-07 15:56 ` Georg C. F. Greve
2001-04-07 17:34 ` Alex Schroeder
[not found] ` <m2snjksjem.fsf@snail.nowhere.ch>
2001-04-08 14:57 ` Georg C. F. Greve
2001-04-08 18:36 ` Kai Großjohann
2001-04-08 19:19 ` Alex Schroeder
2001-04-09 9:26 ` Georg C. F. Greve
2001-04-09 10:06 ` Kai Großjohann
2001-04-08 19:55 ` Georg C. F. Greve
2001-04-08 20:23 ` Kai Großjohann [this message]
2001-04-08 20:38 ` Georg C. F. Greve
2001-04-08 20:41 ` Kai Großjohann
2001-04-09 9:29 ` Georg C. F. Greve
2001-04-09 16:01 ` Dan Christensen
2001-04-09 18:39 ` Paul Jarc
2001-04-09 19:48 ` Kai Großjohann
2001-04-10 15:19 ` Paul Jarc
2001-04-14 21:51 ` Steinar Bang
2001-04-14 22:34 ` Kai Großjohann
2001-04-15 20:30 ` Steinar Bang
2001-04-15 3:52 ` Paul Jarc
2001-04-15 7:58 ` Kai Großjohann
2001-04-15 18:30 ` simon
2001-04-15 20:30 ` Steinar Bang
2001-04-15 23:25 ` Bjørn Mork
2001-04-09 20:10 ` Georg C. F. Greve
2001-04-09 20:36 ` Paul Jarc
2001-04-10 8:34 ` Georg C. F. Greve
2001-04-10 15:38 ` Paul Jarc
2001-04-09 20:50 ` Kai Großjohann
2001-04-10 8:35 ` Georg C. F. Greve
2001-04-10 9:42 ` Kai Großjohann
2001-04-10 9:54 ` Georg C. F. Greve
2001-04-10 9:20 ` nnmail-split-fancy-with-parent (Was: Question about mail archive) Mats Löfdahl
2001-04-10 9:44 ` Kai Großjohann
2001-04-10 10:00 ` Mats Löfdahl
2001-04-10 14:53 ` Kai Großjohann
2001-04-10 16:25 ` Mats Löfdahl
2001-04-10 17:20 ` Kai Großjohann
2001-04-10 14:02 ` Doug Alcorn
2001-04-10 14:55 ` Kai Großjohann
2001-04-11 3:21 ` Question about mail archive Samuel Padgett
2001-04-11 10:07 ` Kai Großjohann
2001-04-11 14:23 ` Paul Jarc
2001-04-13 15:58 ` Kai Großjohann
2001-04-10 1:18 ` Dan Christensen
2001-04-10 8:39 ` Georg C. F. Greve
2001-04-10 0:55 ` Karl Kleinpaste
2001-04-10 15:46 ` Paul Jarc
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=vafbsq7i1in.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=alex@gnu.org \
--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).