From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: Message buffers associated with files?
Date: 02 Oct 1996 00:54:56 +0100 [thread overview]
Message-ID: <x6g23y8cku.fsf@eyesore.no> (raw)
In-Reply-To: Paul Franklin's message of 27 Sep 1996 11:49:20 -0700
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."
next prev parent reply other threads:[~1996-10-01 23:54 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-09-17 20:45 Shane Holder
1996-09-18 1:30 ` Lars Magne Ingebrigtsen
1996-09-18 6:15 ` Steinar Bang
1996-09-19 2:09 ` Lars Magne Ingebrigtsen
1996-09-19 7:06 ` Nathanael Makarevitch
1996-09-19 14:25 ` Colin Rafferty
1996-09-19 17:22 ` Lars Magne Ingebrigtsen
1996-09-19 18:18 ` Eric Hendrickson
1996-09-19 18:51 ` Per Abrahamsen
1996-09-19 19:08 ` William Perry
1996-09-20 6:36 ` Steinar Bang
1996-09-20 13:32 ` Richard Pieri
1996-09-19 9:16 ` Steinar Bang
1996-09-19 16:51 ` Matt Pharr
1996-09-19 17:45 ` luis fernandes
1996-09-20 6:23 ` Andy Eskilsson
1996-09-20 6:34 ` Steinar Bang
1996-09-21 4:41 ` Ken Raeburn
1996-09-21 7:18 ` Lars Magne Ingebrigtsen
1996-09-21 8:10 ` Jason L Tibbitts III
1996-09-24 17:29 ` Lars Magne Ingebrigtsen
1996-09-25 18:24 ` Steven L Baur
1996-09-21 21:48 ` Ken Raeburn
1996-09-27 5:23 ` Usenet news
1996-09-27 15:45 ` Scott Blachowicz
[not found] ` <tx1d8zga39g.fsf@cygnus <199609270523.HAA25994@sunsite.auc.dk>
1996-09-27 17:21 ` Lars Magne Ingebrigtsen
1996-09-27 18:49 ` Paul Franklin
1996-10-01 23:54 ` Lars Magne Ingebrigtsen [this message]
1996-09-19 11:02 ` Jost Krieger
1996-09-19 11:18 ` Lars Balker Rasmussen
1996-09-19 13:58 ` William Perry
1996-09-19 17:26 ` Lars Magne Ingebrigtsen
1996-09-20 6:32 ` Steinar Bang
1996-09-19 12:37 ` Jack Vinson
1996-09-19 17:24 ` Lars Magne Ingebrigtsen
1996-09-19 19:47 ` Steven L Baur
1996-09-20 8:23 ` Lars Balker Rasmussen
1996-09-20 13:06 ` Jack Vinson
1996-09-23 12:06 ` Vegetable Gnus (was: Message buffers associated with files?) Jost Krieger
1996-09-23 17:30 ` Lars Magne Ingebrigtsen
1996-09-24 14:54 ` Robert Pluim
1996-09-25 18:32 ` Steven L Baur
1996-09-25 19:45 ` Lars Magne Ingebrigtsen
1996-09-25 21:47 ` William Perry
1996-09-26 3:37 ` Steven L Baur
1996-09-26 3:45 ` Steven L Baur
1996-09-26 10:27 ` Per Abrahamsen
1996-09-26 10:47 ` Lars Balker Rasmussen
1996-09-26 11:12 ` Hans de Graaff
1996-09-26 13:52 ` Kevin.Christian
1996-09-26 14:15 ` Lars Balker Rasmussen
1996-09-26 15:06 ` Per Abrahamsen
1996-09-26 15:49 ` C. R. Oldham
1996-10-07 21:30 ` Manual generation problem with 0.48 C. R. Oldham
1996-09-26 14:28 ` Vegetable Gnus (was: Message buffers associated with files?) Brent B. Powers
1996-09-26 19:14 ` Lars Magne Ingebrigtsen
1996-09-20 1:44 ` Message buffers associated with files? Ed Donovan
1996-09-20 5:26 ` Lars Magne Ingebrigtsen
1996-09-22 8:32 ` Ed Donovan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=x6g23y8cku.fsf@eyesore.no \
--to=larsi@ifi.uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).