From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/8082 Path: main.gmane.org!not-for-mail From: Lars Magne Ingebrigtsen Newsgroups: gmane.emacs.gnus.general Subject: Re: Message buffers associated with files? Date: 27 Sep 1996 19:21:25 +0200 Message-ID: References: <199609172045.PAA24878@mordor.rsn.hp.com> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Trace: main.gmane.org 1035148302 10031 80.91.224.250 (20 Oct 2002 21:11:42 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 21:11:42 +0000 (UTC) Return-Path: ding-request@ifi.uio.no Original-Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by deanna.miranova.com (8.7.6/8.6.9) with SMTP id KAA05989 for ; Fri, 27 Sep 1996 10:37:01 -0700 Original-Received: from ylfing.ifi.uio.no (ylfing.ifi.uio.no [129.240.94.25]) by ifi.uio.no with ESMTP (8.6.11/ifi2.4) id for ; Fri, 27 Sep 1996 19:21:29 +0200 Original-Received: (from larsi@localhost) by ylfing.ifi.uio.no ; Fri, 27 Sep 1996 19:21:28 +0200 Original-To: ding@ifi.uio.no In-Reply-To: Usenet news's message of Fri, 27 Sep 1996 07:23:25 +0200 (MET DST) Original-Lines: 51 X-Mailer: Red Gnus v0.44/Emacs 19.34 X-Face: &w!^oO~dS|}-P0~ge{$c!h\ channeling Paul Franklin writes: > So here's my wish list for backend capabilities needed by nngnats > (which should be a superset of those needed for a nice nnman): > > * Backends can affect the marks of articles. Hmm. Looks like this is > now possible by coding nngnats-request-update-info. This would be > the time to awake dormant articles when they've changed. Yup. > * Backends can contribute additional fields. Users can limit by these > fields, possibly through a special '/' command which prompts you for > a backend-specific field name. Users can also score on these > fields. (For nngnats, this would include responsible person, > severity, priority, ...) Yes, this is very important, but I haven't made any progress here, I'm afraid. It's on that todo list, though. > * Backends can have persistent, internal state. For nngnats, this > would be the last mod date of the gnats report, and possibly 1-2 > other things so the files don't have to be scanned every time. (Or > maybe this should go into files in a directory specified by a server > parameter. It can't go into a gnats or man dir, since they're > shared dirs.) For nnman, this would be the article numbers of man > pages. (Hmm. Pretty soon, we'll have a .gnus directory for all of > this stuff.) Quite a few of the backends store data to keep a consistant internal state. The latest is nnweb, which creates an URL<->article number mapping and stores that to be able to number things properly. > * Backends should be able to reject incorrectly-formatted messages in > -request-replace-article and -request-accept-article, probably via a > return value. This would allow someone to submit or edit problem > reports from gnus with appropriate checks in place. This is possible -- if the backend returns nil for these functions, the replacement is aborted. > * Backends should be able to lock files for editing, if that's > necessary. (I'm not sure if nngnats actually needs it, but it seems > really useful.) I don't think there's any file locking in Emacs currently, but it would be useful. -- (domestic pets only, the antidote for overdose, milk.) larsi@ifi.uio.no * Lars Ingebrigtsen