From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/23505 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 23:44:27 -0700 Organization: Sun Microsystems, Inc. Sender: owner-ding@hpc.uh.edu Message-ID: <4jyzp1qdrn8.fsf@homeworld.Eng.Sun.Com> References: <4jywvwuyde2.fsf_-_@homeworld.Eng.Sun.Com> <4jy4sjy1s6k.fsf@homeworld.Eng.Sun.Com> <99Jun23.201735edt.13841-3@gateway.intersys.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 1035161226 2377 80.91.224.250 (21 Oct 2002 00:47:06 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 00:47:06 +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 CAA27835 for ; Thu, 24 Jun 1999 02:45:57 -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 BAB25616; Thu, 24 Jun 1999 01:45:24 -0500 (CDT) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Thu, 24 Jun 1999 01:45:49 -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 BAA10867 for ; Thu, 24 Jun 1999 01:45:37 -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 CAA27818 for ; Thu, 24 Jun 1999 02:44:39 -0400 (EDT) Original-Received: from engmail1.Eng.Sun.COM ([129.146.1.13]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id XAA12454; Wed, 23 Jun 1999 23:44:29 -0700 (PDT) Original-Received: from philly.Eng.Sun.COM (philly.Eng.Sun.COM [129.144.140.126]) by engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id XAA02016; Wed, 23 Jun 1999 23:44:28 -0700 (PDT) Original-Received: (from tonyl@localhost) by philly.Eng.Sun.COM (8.9.1b+Sun/8.9.1) id XAA28876; Wed, 23 Jun 1999 23:44:28 -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 "Wed, 23 Jun 1999 20:20:11 -0400" Original-Lines: 42 Precedence: list X-Majordomo: 1.94.jlt7 Xref: main.gmane.org gmane.emacs.gnus.general:23505 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:23505 * "Rat" == Stainless Steel Rat writes: Rat> Point: Gnus *DOES* hide those numbers completely (if you tell it Rat> not to display article numbers in the summary buffers). People are forced to be concern with, deal with article numbers because they have been kept prompting to make decision (how many messages to fetch), for which they have first to be aware there is an article number associate with each article and secondly, they have to somehow keep reseqencing these numbers in order for that decision to make sense. And for the situations I mentioned, Gnus does not provide a satisfactory solution. Rat> Admittedly, you are using cache and tick in a fashion that is Rat> more complex than it needs to be (read: wrong :). I think you Rat> would be happier doing this: Rat> * Use ticks (! or u) to mark articles that you wish to reply to later. Rat> * Use mark dormant (?) to mark articles that you want to keep around Rat> forever. Rat> * Set gnus-use-cache based on group name (I use a cond form in Rat> gnus-select-group-hook to set certain variables based on group name). Rat> Set it true for remote groups, nil or passive as you would for local Rat> (mail) groups. I'm one of those people who prefer 5 marks for messages: unmarked - new message O - old, read message (with total-expire) ! - message needs attention * - message archived in place ? - interesting message that I would like to see followup Anyway, the problem remains as long as any kind of cache is used for mail groups (gnus-use-cache is anything other than nil) and I don't see how using cache is too complex. Regards, Tony