From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/8087 Path: main.gmane.org!not-for-mail From: Paul Franklin Newsgroups: gmane.emacs.gnus.general Subject: Re: Message buffers associated with files? Date: 27 Sep 1996 11:49:20 -0700 Organization: Computer Science, U of Washington, Seattle, WA, USA Sender: paul@cs.washington.edu Message-ID: References: <199609172045.PAA24878@mordor.rsn.hp.com> NNTP-Posting-Host: coloc-standby.netfonds.no X-Trace: main.gmane.org 1035148306 10059 80.91.224.250 (20 Oct 2002 21:11:46 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 21:11:46 +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 MAA07584 for ; Fri, 27 Sep 1996 12:09:42 -0700 Original-Received: from june.cs.washington.edu (june.cs.washington.edu [128.95.1.4]) by ifi.uio.no with ESMTP (8.6.11/ifi2.4) id for ; Fri, 27 Sep 1996 20:49:26 +0200 Original-Received: from fester.cs.washington.edu (fester.cs.washington.edu [128.95.4.119]) by june.cs.washington.edu (8.7.5/7.2ju) with ESMTP id LAA17942 for ; Fri, 27 Sep 1996 11:49:23 -0700 Original-Received: (from paul@localhost) by fester.cs.washington.edu (8.6.12/8.6.9) id LAA01506; Fri, 27 Sep 1996 11:49:23 -0700 Original-To: ding@ifi.uio.no Original-Lines: 41 X-Newsreader: Red Gnus v0.34/Emacs 19.34 In-Reply-To: Lars Magne Ingebrigtsen's message of 27 Sep 1996 19:21:25 +0200 Xref: main.gmane.org gmane.emacs.gnus.general:8087 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:8087 BTW, Lars, for the record, gnus5 has substantially increase the amount of time I spend hacking elisp code. I'm not sure whether that's a good thing or not. But it is fun. >>>>> Lars Magne Ingebrigtsen writes: > Usenet news channeling Paul Franklin writes: >> * 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. Cool! I didn't find this in the docs, but I may not have the latest rev. In my version, this option isn't mentioned for -request-accept-article, and the docs for -request-replace-article, -request-delete-group, and -request-rename-group don't mention return values. >> * 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. This wasn't quite what I was thinking of. If I recall correctly, editpr in gnats implements some sort of file locking. I'd like to use that mechanism to restrict editing nngnats messages. Since -request-replace-article is presumably called when an edit finishes, I just need to know when an edit starts or is cancelled (including killing the edit buffer). This may be particular enough to nngnats that it should maybe wait until there's someone to actually code it though, since I'm no longer a gnats user. --Paul