From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/23501 Path: main.gmane.org!not-for-mail From: Tony Lam Newsgroups: gmane.emacs.gnus.general Subject: Re: Being forced to deal with message numbers and frustrated Date: 23 Jun 1999 15:13:39 -0700 Organization: Sun Microsystems, Inc. Sender: owner-ding@hpc.uh.edu Message-ID: <4jy4sjy1s6k.fsf@homeworld.Eng.Sun.Com> References: <4jywvwuyde2.fsf_-_@homeworld.Eng.Sun.Com> 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 1035161222 2361 80.91.224.250 (21 Oct 2002 00:47:02 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 00:47:02 +0000 (UTC) Cc: "(ding)" Return-Path: Original-Received: from farabi.math.uh.edu (farabi.math.uh.edu [129.7.128.57]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id SAA18471 for ; Wed, 23 Jun 1999 18:14:51 -0400 (EDT) Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5]) by farabi.math.uh.edu (8.9.1/8.9.1) with ESMTP id RAB21344; Wed, 23 Jun 1999 17:14:24 -0500 (CDT) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Wed, 23 Jun 1999 17:14:58 -0500 (CDT) Original-Received: from sclp3.sclp.com (root@sclp3.sclp.com [204.252.123.139]) by sina.hpc.uh.edu (8.9.3/8.9.3) with ESMTP id RAA04904 for ; Wed, 23 Jun 1999 17:14:46 -0500 (CDT) Original-Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id SAA18443 for ; Wed, 23 Jun 1999 18:13:48 -0400 (EDT) Original-Received: from engmail3.Eng.Sun.COM ([129.144.170.5]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA00603; Wed, 23 Jun 1999 15:13:41 -0700 (PDT) Original-Received: from philly.Eng.Sun.COM (philly.Eng.Sun.COM [129.144.140.126]) by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id PAA29872; Wed, 23 Jun 1999 15:13:40 -0700 (PDT) Original-Received: (from tonyl@localhost) by philly.Eng.Sun.COM (8.9.1b+Sun/8.9.1) id PAA27896; Wed, 23 Jun 1999 15:13:40 -0700 (PDT) X-Mailer: 20.4 "Emerald" XEmacs Lucid (via feedmail 9-beta-4 I); Gnus v5.6.45/XEmacs 20.4 - "Emerald" Original-To: Stainless Steel Rat In-Reply-To: Stainless Steel Rat's message of "23 Jun 1999 15:56:49 -0400" Original-Lines: 71 Precedence: list X-Majordomo: 1.94.jlt7 Xref: main.gmane.org gmane.emacs.gnus.general:23501 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:23501 * "Rat" == Stainless Steel Rat writes: * Tony Lam on Wed, 23 Jun 1999 Tony> * Number gap in cached messages can not be removed. When a messages Tony> group (I use nnfolder) has cached articles, I find Tony> respooling/moving/copying messages in the group do not touch Tony> cached articles, Rat> Why are you caching mail messages? There is no sane reason to do Rat> more than 'tick' with `u' so as to prevent articles from being Rat> expired. I use passive cache to archive messages in the same group in mail and news because ticked messages can be expired, at least in newsgroups, and I want one consistent operation for both mail and groups. Besides, I use tick to mark messages that need to be replied later. >>From Gnus's info: `!' Marked as ticked (`gnus-ticked-mark'). "Ticked articles" are articles that will remain visible always. If you see an article that you find interesting, or you want to put off reading it, or replying to it, until sometime later, you'd typically tick it. However, articles can be expired, so if you want to keep an article forever, you'll have to make it persistent (*Note Persistent Articles::). Maybe the problem can be better stated as article number reseqencing is not possible for mail groups with cached articles. Tony> also cache groups do not support moving/copy themselves, Rat> There is no "cache" backend. The only ways to read cache areas Rat> is to use nndir or nneething backends, both of which are Rat> read-only backends. Rat> If you wish to reseqence a group, process mark all messages in Rat> that group and move them to the same group (B m). You're right, there is no "nncache" backend. My cache groups are using nnspool backends (Gnus's default?) I was referring the groups that I setup to read cached only articles. My point was that those groups do not support copying/moving, so I can't copy or move them to remove number gaps. Rat> Virtual groups are frustrating :). Rat> Gnus reads 100 articles. Good to know. Still they are not the last 300 articles that are arrived most recently from the point of virtual group, as I would get from a non-virtual group (assuming no article number gap off course). Rat> I've never experienced these "problems", mainly becuase I never Rat> bother thinking about things like article numbers. They are Rat> irrelevant to me; they only mean something to the Gnus backend Rat> that maintains them. Ignore messages numbers and your "problems" Rat> will go away. I never want to care about article numbers in the first place. Gnus could have transparently hide those numbers from user completely, or at least provide some satisfactory working solution that can be automated to deal with these situations, and there would be no problems from user regarding article numbers. Regards, Tony