From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/11419 Path: main.gmane.org!not-for-mail From: Scott Blachowicz Newsgroups: gmane.emacs.gnus.general Subject: Re: TODO idea: Date: Fri, 20 Jun 1997 11:16:49 -0700 Message-ID: References: Reply-To: scott@statsci.com NNTP-Posting-Host: coloc-standby.netfonds.no X-Trace: main.gmane.org 1035151129 30135 80.91.224.250 (20 Oct 2002 21:58:49 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 21:58:49 +0000 (UTC) Cc: ding@ifi.uio.no Return-Path: Original-Received: from sandy.calag.com (root@sandy [206.190.83.128]) by altair.xemacs.org (8.8.5/8.8.5) with ESMTP id OAA06833 for ; Fri, 20 Jun 1997 14:58:10 -0700 Original-Received: from xemacs.org (xemacs.cs.uiuc.edu [128.174.252.16]) by sandy.calag.com (8.8.5/8.8.5) with ESMTP id OAA19033 for ; Fri, 20 Jun 1997 14:58:45 -0700 Original-Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by xemacs.org (8.8.5/8.8.5) with SMTP id PAA13758 for ; Fri, 20 Jun 1997 15:31:09 -0500 (CDT) Original-Received: from cliffy.statsci.com (root@cliffy.statsci.com [206.63.206.72]) by ifi.uio.no with ESMTP (8.6.11/ifi2.4) id for ; Fri, 20 Jun 1997 20:17:13 +0200 Original-Received: from apple.statsci.com (apple [206.63.206.4]) by cliffy.statsci.com (8.8.6/8.8.6/Hub) with SMTP id LAA20396; Fri, 20 Jun 1997 11:16:53 -0700 Original-Received: from apple.statsci.com [206.63.206.4] with smtp by apple.statsci.com with smtp (/\oo/\ Smail3.1.29.1 #29.3 #3) id m0wf8Et-0006uMC; Fri, 20 Jun 97 11:16 PDT Original-To: Wesley Hardaker In-reply-to: Your message of "20 Jun 1997 11:12:25 +0200." Original-Lines: 28 Original-Xref: altair.xemacs.org dgnus-list:1809 Xref: main.gmane.org gmane.emacs.gnus.general:11419 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:11419 >>>>> "Wes" == Wesley Hardaker Scott> Let's say instead that you read article 18 instead of 17. Then Scott> you end up with an unseen seq of 8,16,17 and when you do your Scott> 'inc', you end up with a new article 18 (instead of 19). Wes> You forgot to mention you deleted 18 also, not just read it. True, but I was thinking that while writing - does that count? :-)) Wes> However, my general thoughts on this is that if you do a mh 'inc', you Wes> should simply never do a mh 'rmm last'. Period. I wonder how hard it would be to get mh/nmh to use different methods to decide what a new message is to be numbered... 1) add a "lastused" sequence to .mh_sequence that it updates and uses to determined what the next message is to be called. 2) add checks to prevent 'rmm' from really deleting the 'last' message? Maybe just truncate the file? Or rename it to some special name (e.g. "=383" instead of ",383"), then it's existence could be used as a marker similar to that "lastused" sequence? I think I like #1 better. Scott Blachowicz Ph: 206/283-8802x240 Mathsoft (Data Analysis Products Div) 1700 Westlake Ave N #500 scott@statsci.com Seattle, WA USA 98109 Scott.Blachowicz@seaslug.org