From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/11721 Path: main.gmane.org!not-for-mail From: Colin Rafferty Newsgroups: gmane.emacs.gnus.general Subject: Re: [Q] same message in multiple groups & expiry Date: 18 Jul 1997 16:12:09 -0400 Message-ID: References: NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII X-Trace: main.gmane.org 1035151387 32097 80.91.224.250 (20 Oct 2002 22:03:07 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 22:03:07 +0000 (UTC) Cc: Michael.Huehne@Germany.EU.net, Ulrich Pfeifer , Norbert Goevert , Torsten Polle Return-Path: Original-Received: from xemacs.org (xemacs.cs.uiuc.edu [128.174.252.16]) by altair.xemacs.org (8.8.6/8.8.6) with ESMTP id OAA14863 for ; Fri, 18 Jul 1997 14:53:26 -0700 Original-Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by xemacs.org (8.8.5/8.8.5) with SMTP id QAA09548 for ; Fri, 18 Jul 1997 16:50:03 -0500 (CDT) Original-Received: from claymore.vcinet.com (claymore.vcinet.com [208.205.12.23]) by ifi.uio.no with SMTP (8.6.11/ifi2.4) id for ; Fri, 18 Jul 1997 22:40:56 +0200 Original-Received: (qmail 19601 invoked by uid 504); 18 Jul 1997 20:14:11 -0000 Original-Received: (qmail 19598 invoked from network); 18 Jul 1997 20:14:10 -0000 Original-Received: from softdnserror (HELO wfdutilgw.ml.com) (206.3.74.31) by claymore.vcinet.com with SMTP; 18 Jul 1997 20:14:10 -0000 Original-Received: from ml1.ml.com ([199.201.57.130]) by wfdutilgw.ml.com (8.8.5/8.8.5/MLgw-3.03) with ESMTP id QAA02440; Fri, 18 Jul 1997 16:08:03 -0400 (EDT) Original-Received: from commpost.ml.com (commpost.ml.com [146.125.4.24]) by ml1.ml.com (8.8.5/8.8.5/MLml4-2.07) with SMTP id QAA15225; Fri, 18 Jul 1997 16:11:49 -0400 (EDT) Original-Received: from spssunp.spspme.ml.com (spssunp.spspme.ml.com [192.168.111.13]) by commpost.ml.com (8.6.12/8.6.12) with ESMTP id QAA14621; Fri, 18 Jul 1997 16:16:48 -0400 Original-Received: by spssunp.spspme.ml.com (SMI-8.6/SMI-4.1) id QAA01072; Fri, 18 Jul 1997 16:12:10 -0400 Original-To: (ding) GNUS Mailing List X-Face: ""xJff%{>hr-{:QXl"Xk2O@@(+F]e{"%EYQiW@mUuvEsL>=mx96j12qW[%m;|:B^n{J8k?Mz[K1_+H;$v,nYx^1o_=4M,L+]FIU~[[`-w~~xsy-BX,?tAF_.8u&0y*@aCv;a}Y'{w@#*@iwAl?oZpvvv X-Y-Zippy: .. here I am in 53 B.C. and all I want is a dill pickle!! In-Reply-To: Kai Grossjohann's message of "18 Jul 1997 18:24:17 +0200" Original-Lines: 90 X-Mailer: Gnus v5.4.62/XEmacs 20.3(beta12) - "Helsinki" Xref: main.gmane.org gmane.emacs.gnus.general:11721 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:11721 Kai Grossjohann writes: > I'm thinking about revising my strategy of dealing with mail. Up to > now, I had few folders and have put each mail into exactly one > folder. This has saved me from lots of potential problems that arise > if you put messages into several folders at once. What problems are these? I haven't seen any in close to two years of using Gnus. > (FWIW, I do not use total-expire.) > If a message has been put into groups A and B by the splitting process > there are a number of operations that I'd like to perform with the > message, while in group A. I'll formulate the operations in terms of > "copies" (even though they might be hard links or whatnot), and I'll > disregard nnmail-expiry-wait and speak as if a message marked as > expirable will be deleted from disk immediately. > (1) Remove the group A copy but keep the group B copy. Mark the group > B copy as read or dormant or something (optional). If you enter group A and read the article, all its cross-postings are marked as read everywhere (just as a cross-posted new article). The article in group B will be marked read, but without total-expire, it will not be marked as expirable. > (2) Delete all copies of this message. Difficult. Reading the article in A will expire the article in group B if and only if group B is total-expire. Otherwise, you would need to roll your own (as far as I know). Of course, there is an Xref field in the article in A, so that can help a little. > (3) Move the group A copy into group C but keep the group B copy as it > is. I don't care what mark the group B copy will have. `B m' (gnus-summary-move-article). The group B article version will be marked read if and only if the group A article was marked as read before you move it. > (4) Remove all copies of this message and put a new copy of it into > group C. Well, the remove all copies is tough (see (2)), but putting a new copy into group C would be just `e'dit the article, and then `B m'ove it. > (5) Put an additional copy into group C. `B c' (gnus-summary-copy-article). > Also, I'm unsure of what the following operations will do: > - Mark as expirable; does this correspond to (1) or (2), or > something else entirely? It corresponds to (1). The "read" mark is set if and only if you have the "read" mark in group A. > - "B c" should be fairly clear, it's operation (5), isn't it. Exactly. > - "B m"; does this correspond to (3) or to (4)? It corresponds to (3). > How does total-expire interact with all of this? It automatically does what you want for (2), but not what you want for (1). > How have your experiences been with splitting mail to be put into > several groups? Pretty good. I have total-expire set in my groups that mail is split into, and different expiration times set for different classes of groups. I would suggest total-expire with intelligent expiration times. I use `?' on articles that I really want to keep forever, or I just `B c' them into "archive" groups that do not match `gnus-total-expirable-newsgroups'. I hope that this has helped. -- Colin