From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/32879 Path: main.gmane.org!not-for-mail From: prj@po.cwru.edu (Paul Jarc) Newsgroups: gmane.emacs.gnus.general Subject: Re: "Fixing up" gnus - (how hard is this?). Date: 17 Oct 2000 16:29:11 -0400 Sender: owner-ding@hpc.uh.edu Message-ID: References: <87aec3o3u6.fsf_-_@raven.localnet> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035169087 22256 80.91.224.250 (21 Oct 2002 02:58:07 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 02:58:07 +0000 (UTC) Return-Path: Original-Received: from spinoza.math.uh.edu (spinoza.math.uh.edu [129.7.128.18]) by mailhost.sclp.com (Postfix) with ESMTP id AE59CD051E for ; Tue, 17 Oct 2000 16:31:10 -0400 (EDT) Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5]) by spinoza.math.uh.edu (8.9.1/8.9.1) with ESMTP id PAB27242; Tue, 17 Oct 2000 15:30:12 -0500 (CDT) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Tue, 17 Oct 2000 15:29:22 -0500 (CDT) 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 PAA25395 for ; Tue, 17 Oct 2000 15:29:12 -0500 (CDT) Original-Received: from multivac.student.cwru.edu (multivac.STUDENT.CWRU.Edu [129.22.239.69]) by mailhost.sclp.com (Postfix) with SMTP id 342D4D051E for ; Tue, 17 Oct 2000 16:29:38 -0400 (EDT) Original-Received: (qmail 25464 invoked by uid 500); 17 Oct 2000 20:29:33 -0000 Mail-Followup-To: ding@gnus.org Original-To: ding@gnus.org In-Reply-To: Rob Browning's message of "17 Oct 2000 11:00:17 -0500" Original-Lines: 43 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:32879 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:32879 Rob Browning writes: > One of my gripes is that you can't easily just archive a group (by > copying/moving directories), and have gnus DTRT. This is both > because gnus doesn't store the readness info with the files, Backends can do this. If all backends were made to do this, Gnus wouldn't have to duplicate the information in newsrc.eld, and nn*-request-set-info could perhaps be discarded in favor of -get-article-marks, -get-marked-articles, etc. > and because gnus keeps its own idea about where your groups are - it > doesn't just present you with whatever groups it finds in the nnml > source directory. I think backends can also tackle this problem. I intend to do so for nnmaildir. > - it should be *very* hard to have an emacs crash totally hose all > your state information (readness, group hierarchies, layout, > etc.). This means storing the mark info with the backend *and* > writing it frequently - this may mean *not* writing out a > monolihic state file, not even one per backend group. nnmaildir writes its state file frequently, but it is one monolithic file per group. I may move to some form of journaling, but I've got other changes to get to first. > - it should allow every article to be marked with an arbitrary > number of "tags". User-defined, you mean? That would be useful indeed. Obviously, it requires cooperation from Gnus, though. > I've also wondered how hard it might be to turn much of the gnus code > into a mail related emacs library. That would be good. Gnus, and user applications in general, ought to consist of largely application-independant, reusable code, along with some UI-specific code and (user-redefinable, of course) bindings to that UI code. paul