From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/33606 Path: main.gmane.org!not-for-mail From: Jan Nieuwenhuizen Newsgroups: gmane.emacs.gnus.general Subject: Re: how does expiry-target work? Date: 09 Dec 2000 14:00:29 +0100 Organization: Jan at Appel Sender: owner-ding@hpc.uh.edu Message-ID: References: <200012061525.QAA18265@appel.lilypond.org> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: main.gmane.org 1035169681 26000 80.91.224.250 (21 Oct 2002 03:08:01 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 03:08:01 +0000 (UTC) Cc: ding@gnus.org Return-Path: Original-Received: from lisa.math.uh.edu (lisa.math.uh.edu [129.7.128.49]) by mailhost.sclp.com (Postfix) with ESMTP id D22C7D049A for ; Sat, 9 Dec 2000 08:02:42 -0500 (EST) Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5]) by lisa.math.uh.edu (8.9.1/8.9.1) with ESMTP id HAB10775; Sat, 9 Dec 2000 07:02:37 -0600 (CST) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Sat, 09 Dec 2000 07:00:21 -0600 (CST) Original-Received: from mailhost.sclp.com (postfix@66-209.196.61.interliant.com [209.196.61.66] (may be forged)) by sina.hpc.uh.edu (8.9.3/8.9.3) with ESMTP id HAA05717 for ; Sat, 9 Dec 2000 07:00:11 -0600 (CST) Original-Received: from appel.lilypond.org (node1600a.a2000.nl [24.132.96.10]) by mailhost.sclp.com (Postfix) with ESMTP id 98A9CD049A for ; Sat, 9 Dec 2000 08:00:33 -0500 (EST) Original-Received: from appel.lilypond.org.appel (appel.lilypond.org [24.132.96.10]) by appel.lilypond.org (8.9.3/8.9.3) with ESMTP id OAA19008; Sat, 9 Dec 2000 14:00:29 +0100 X-Authentication-Warning: appel.lilypond.org: Host appel.lilypond.org [24.132.96.10] claimed to be appel.lilypond.org.appel Original-To: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "09 Dec 2000 04:13:37 +0100" Original-Lines: 39 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 Precedence: list X-Majordomo: 1.94.jlt7 Xref: main.gmane.org gmane.emacs.gnus.general:33606 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:33606 Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Gro=DFjohann) writes: > Why does using pick require that you use nnmh and not nnml? Reading > nnml groups works just fine using the MH tools, but you have to be > extremely careful not to modify the ~/Mail directory in any way. Ah, of course! And, what if I do modify the ~/Mail directory by accident, or as a variation on that question, how can I convert my nnmh groups to nnml? I guess that nnml is one of *the* backends to use, right? Btw, I fixed a bug in my expiry-target patch for nnmh. I've been using it now for a few days, and it seems to work fine. Maybe you(?) want to include it in Gnus? > Do you think a search engine backend for nnir.el would be useful that > uses pick? 13:41:35 appel ~$ locate nnir.el 13:41:39 appel ~$=20 As you can see, I'll have to look at nnir.el first, google will probably help me. But, I've always found pick to be very effective, (and didn't get immediate scoring to work. will look at nnir) it is one of the two last nmh features I still use. The other one is not really an nmh feature: I've written a crude script ``rpatch' that reads the current message, tries various unpack methods to find the patch, find a sensible name if none is specified, eg (-..diff.gz>) patches, save and possibly apply it (to LilyPond). Maybe you happen to have some lisp code that does parts of that? Greetings, Jan. --=20 Jan Nieuwenhuizen | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org