From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/44885 Path: main.gmane.org!not-for-mail From: Josh Huber Newsgroups: gmane.emacs.gnus.general Subject: Re: funny problems with nnmail-cache and split-fancy-with-parent Date: Mon, 20 May 2002 17:32:01 -0400 Sender: owner-ding@hpc.uh.edu Message-ID: <87g00mtsj2.fsf@alum.wpi.edu> References: <87offy9v9p.fsf@alum.wpi.edu> <87vga5xnfc.fsf@alum.wpi.edu> <87n0vh13er.fsf@alum.wpi.edu> <87r8ko822k.fsf@alum.wpi.edu> <87661sqgsc.fsf@alum.wpi.edu> <87661pcwbo.fsf@alum.wpi.edu> <87g00t9vjg.fsf@alum.wpi.edu> <87u1p2vrn1.fsf@alum.wpi.edu> <873cwmvfan.fsf@alum.wpi.edu> NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: main.gmane.org 1021930260 31529 127.0.0.1 (20 May 2002 21:31:00 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 20 May 2002 21:31:00 +0000 (UTC) Return-path: Original-Received: from malifon.math.uh.edu ([129.7.128.13]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 179uk8-0008CQ-00 for ; Mon, 20 May 2002 23:31:00 +0200 Original-Received: from sina.hpc.uh.edu ([129.7.128.10] ident=lists) by malifon.math.uh.edu with esmtp (Exim 3.20 #1) id 179uk3-0004Xo-00; Mon, 20 May 2002 16:30:55 -0500 Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Mon, 20 May 2002 16:31:13 -0500 (CDT) Original-Received: from sclp3.sclp.com (qmailr@sclp3.sclp.com [209.196.61.66]) by sina.hpc.uh.edu (8.9.3/8.9.3) with SMTP id QAA06035 for ; Mon, 20 May 2002 16:30:57 -0500 (CDT) Original-Received: (qmail 8613 invoked by alias); 20 May 2002 21:30:33 -0000 Original-Received: (qmail 8608 invoked from network); 20 May 2002 21:30:33 -0000 Original-Received: from quimby.gnus.org (80.91.224.244) by gnus.org with SMTP; 20 May 2002 21:30:33 -0000 Original-Received: from news by quimby.gnus.org with local (Exim 3.12 #1 (Debian)) id 179uxH-0001Fl-00 for ; Mon, 20 May 2002 23:44:35 +0200 Original-To: ding@gnus.org Original-Path: not-for-mail Original-Newsgroups: gnus.ding Original-Lines: 71 Original-NNTP-Posting-Host: lowell.missioncriticallinux.com Original-X-Trace: quimby.gnus.org 1021931075 3647 64.244.21.16 (20 May 2002 21:44:35 GMT) Original-X-Complaints-To: usenet@quimby.gnus.org Original-NNTP-Posting-Date: 20 May 2002 21:44:35 GMT X-PGP-KeyID: 6B21489A X-Face: C%mBb*K1^od)w'=CH$WEZu/M^aR<,.n|1uAe,;MyNLKoel>F;-j[`L!>m:Y%/R}m&4&xuIM R%7Ez?vbd*Ns>VE;{\(yl|mGByV{D:Dm>'52].@P&t_s^,.d Maybe my wording was unclear. By ^M I mean character number 13, aka > CR. I don't mean the two characters ^ and M. I think ascii 13 is > not allowed in group names. Right, I understood -- sorry I was unclear. > The ^M is at EOL. So this smells of a DOSish file. But of course I > have no idea where these characters come from. Here is a typical ^M > inflicted line: > > Quite odd, eh? > Hm. Now that I look at the file it seems that most message ids are > from me. Strange. And all the ^M lines seem to come from messages I > sent from an nnimap group. (I have magic in my .gnus file to put a > token in the msg id so that I can file followups in the same group as > their originals.) This looks pretty strange, but I guess it's not somehow getting that character as the group name, otherwise there would be a tab separating the two fields. Does anyone else see ^M's in their cache file? > Hm? I think you're looking in the wrong place for the problems. I > think it's entirely sufficient to put group names such as > nnml+private:foo.bar into the file. Right -- absolutely. When you said backward compatibility, I thought you meant allowing older Gnus to function with .nnmail-cache files generated by the newer versions. > The only problem is that the natural interpretation for `bare' group > names is that they come from the primary (native) server. But this > is clearly not the case for the old group names. Right... > Another possibility would be to define a third field. Lines with > only one field are old lines without group name. Lines with two > fields are old lines with group name. Lines with three fields > include the server, where an empty third field could mean the native > server. Otherwise the third field could have a form such as > nnml:foo (like shown in the server buffer). This sounds like a step in the right direction. I'll have to think about it some more though. I really think the differentiation between the primary server and the secondary servers to be one of the more confusing/annoying things about gnus. Personally, requiring the prefix (i.e. "nnml:") before even the primary server should be required, or at least used internally. I'd like it to be done it such a way that there was no distiction...just gnus-server-list. (for example). The user could then have the option to hide the prefix in the group view, and use group names without the prefix. If any ambiguities occured (the same group from different servers) the different part could be shown in the group buffer. Of course, this would take a lot of work, and I'm sure there are many problems lurking which would make this very difficult. Thoughts? -- Josh Huber