From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/34534 Path: main.gmane.org!not-for-mail From: prj@po.cwru.edu (Paul Jarc) Newsgroups: gmane.emacs.gnus.general Subject: Re: Eliminating repetitious "Re: Re: Re: ..." Date: 02 Feb 2001 16:22:50 -0500 Sender: owner-ding@hpc.uh.edu Message-ID: References: <5bzog761e2.fsf@avocet.cs.rochester.edu> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035170443 30921 80.91.224.250 (21 Oct 2002 03:20:43 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 03:20:43 +0000 (UTC) Return-Path: Original-Received: from karazm.math.uh.edu (karazm.math.uh.edu [129.7.128.1]) by mailhost.sclp.com (Postfix) with ESMTP id AD431D049D for ; Fri, 2 Feb 2001 16:24:57 -0500 (EST) Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5]) by karazm.math.uh.edu (8.9.3/8.9.3) with ESMTP id PAC17892; Fri, 2 Feb 2001 15:23:29 -0600 (CST) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Fri, 02 Feb 2001 15:22:33 -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 PAA08200 for ; Fri, 2 Feb 2001 15:22:24 -0600 (CST) Original-Received: from multivac.cwru.edu (multivac.STUDENT.CWRU.Edu [129.22.96.25]) by mailhost.sclp.com (Postfix) with SMTP id 5498FD049D for ; Fri, 2 Feb 2001 16:22:53 -0500 (EST) Original-Received: (qmail 11367 invoked by uid 500); 2 Feb 2001 21:23:12 -0000 Mail-Followup-To: ding@gnus.org Original-To: ding@gnus.org In-Reply-To: ShengHuo ZHU's message of "31 Jan 2001 13:07:49 -0500" User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 Precedence: list X-Majordomo: 1.94.jlt7 Original-Lines: 26 Xref: main.gmane.org gmane.emacs.gnus.general:34534 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:34534 I've thought of adding something like the following to nnmaildir, although it really belongs in Gnus proper, not in backends: I look at a group/topic paramter called, say, canonicalize-subject. Its value is a function. I call that function, giving it the actual subject as an argument. It returns a canonicalized subject. I use the canonicalized subject for NOV data, but leave the original article unmodified. Some useful default things that could be done to the subject: - remove "\`\(Re:|[blah]| *\)*" - remove "(was: .*\'" - replace " +" with " " It looks like a hook might be more appropriate, but then the individual functions would all have to look at a variable instead of their arguments, and set the variable instead of return the new subject. Or else the functions would have to be called by a helper function, instead of in the usual hook fashion. The article itself should not be modified. The canonicalized subject should be used for thread gathering, display in the Summary buffer, constructing replies, and maybe even article display (but not for C-u g, of course). If I do this in my backend by canonicalizing the NOV subject, I'd be able to hit some of these areas, but not all. paul