From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/11420 Path: main.gmane.org!not-for-mail From: Richard Coleman Newsgroups: gmane.emacs.gnus.general Subject: Re: TODO idea: Date: Fri, 20 Jun 1997 17:32:28 -0400 Message-ID: <199706202132.RAA09649@redwood.skiles.gatech.edu> References: NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035151130 30136 80.91.224.250 (20 Oct 2002 21:58:50 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 21:58:50 +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 QAA08729 for ; Fri, 20 Jun 1997 16:32:49 -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 QAA20423 for ; Fri, 20 Jun 1997 16:32:59 -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 SAA15113 for ; Fri, 20 Jun 1997 18:32:25 -0500 (CDT) Original-Received: from euclid.skiles.gatech.edu (root@euclid.skiles.gatech.edu [130.207.146.50]) by ifi.uio.no with ESMTP (8.6.11/ifi2.4) id for ; Fri, 20 Jun 1997 23:36:48 +0200 Original-Received: from redwood.skiles.gatech.edu (root@redwood.skiles.gatech.edu [130.207.146.12]) by euclid.skiles.gatech.edu (8.7.3/8.7.3) with ESMTP id RAA13022; Fri, 20 Jun 1997 17:32:39 -0400 (EDT) Original-Received: from redwood.skiles.gatech.edu (coleman@localhost [127.0.0.1]) by redwood.skiles.gatech.edu (8.8.5/8.8.5) with ESMTP id RAA09649; Fri, 20 Jun 1997 17:32:28 -0400 (EDT) X-Mailer: exmh version 1.6.9 8/22/96 Original-To: scott@statsci.com In-reply-to: Your message of "Fri, 20 Jun 1997 11:16:49 PDT." Original-Lines: 22 Original-Xref: altair.xemacs.org dgnus-list:1810 Xref: main.gmane.org gmane.emacs.gnus.general:11420 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:11420 > 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. It would be very difficult to change the way that MH/nmh handles folders. The code is not very modular. I've been working on cleaning this up for nmh-0.15. So it might be possible in the future, but not now. Richard Coleman coleman@math.gatech.edu