From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/8155
Path: main.gmane.org!not-for-mail
From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Newsgroups: gmane.emacs.gnus.general
Subject: Re: Message buffers associated with files?
Date: 02 Oct 1996 00:54:56 +0100
Message-ID: <x6g23y8cku.fsf@eyesore.no>
References: <199609172045.PAA24878@mordor.rsn.hp.com> 	<x6sp8gvcd1.fsf@eyesore.no> <whrao0l55z.fsf@brage.metis.no> 	<x6loe7ntl5.fsf@eyesore.no> <wh3f0evp8z.fsf@norne.metis.no> 	<tx1d8zga39g.fsf@cygnus <199609270523.HAA25994@sunsite.auc.dk> 	<w8sranng9gq.fsf@ylfing.ifi.uio.no> <r9qzq2baj4f.fsf@fester.cs.washington.edu>
NNTP-Posting-Host: coloc-standby.netfonds.no
X-Trace: main.gmane.org 1035148362 10431 80.91.224.250 (20 Oct 2002 21:12:42 GMT)
X-Complaints-To: usenet@main.gmane.org
NNTP-Posting-Date: Sun, 20 Oct 2002 21:12: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 SAA12784 for <steve@miranova.com>; Tue, 1 Oct 1996 18:24:16 -0700
Original-Received: from ylfing.ifi.uio.no (4867@ylfing.ifi.uio.no [129.240.94.25]) by ifi.uio.no with ESMTP (8.6.11/ifi2.4) 
	id <DAA04804@ifi.uio.no> for <ding@ifi.uio.no> ; Wed, 2 Oct 1996 03:03:07 +0200
Original-Received: (from larsi@localhost) by ylfing.ifi.uio.no ; Wed, 2 Oct 1996 03:03:04 +0200
Original-To: ding@ifi.uio.no
In-Reply-To: Paul Franklin's message of 27 Sep 1996 11:49:20 -0700
Original-Lines: 27
X-Mailer: Red Gnus v0.47/Emacs 19.29
X-Face: &w!^oO<W.WBH]FsTP:P0f9X6M-ygaADlA_)eF$<UwQzj7:C=Gi<a?/_4$LX^@$Qq7-O&XHp
 lDARi8e8iT<(A$LWAZD*xjk^')/wI5nG;1cNB>~dS|}-P0~ge{$c!h\<y
Xref: main.gmane.org gmane.emacs.gnus.general:8155
X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:8155

Paul Franklin <paul@cs.washington.edu> writes:

> 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.

I think this is only mentioned one place -- in the "Backend Interface"
section:

   Functions that fail should return `nil' as the return value.

> 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).

Ah, right.  I could add a new backend function --
`nn*-request-lock-article' (or something) if you think that's
required.  (We'd also need `nn*-request-release-article', I guess.)

-- 
  "Yes.  The journey through the human heart 
     would have to wait until some other time."