From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: "Fixing up" gnus - (how hard is this?). (was Re: (provide 'nnmaildir))
Date: 20 Oct 2000 11:21:57 +0200 [thread overview]
Message-ID: <vafg0lr50lm.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m3aec0olz1.fsf@multivac.student.cwru.edu>
On 19 Oct 2000, Paul Jarc wrote:
> I'd especially like to see documentation of what triggers each
> backend function, and what assumptions, if any, they can make about
> their environment - current buffer, etc.
It took me a while to understand the documentation, but I think that
the Gnus info file does mention all the important things. Or do you
find the node `Backend Interface' deficient in some way?
There was something about the `data buffer' which I didn't understand
right away. The key issue is to understand that `there should be no
data returned' does NOT refer to the return value of the function, but
to the data buffer.
kai
--
I like BOTH kinds of music.
next prev parent reply other threads:[~2000-10-20 9:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-17 16:00 Rob Browning
2000-10-17 20:29 ` "Fixing up" gnus - (how hard is this?) Paul Jarc
2000-10-17 22:53 ` Rob Browning
2000-10-17 20:51 ` "Fixing up" gnus - (how hard is this?). (was Re: (provide 'nnmaildir)) Simon Josefsson
2000-10-17 22:32 ` Rob Browning
2000-10-18 15:13 ` Paul Jarc
2000-10-18 20:07 ` Rob Browning
2000-10-18 20:29 ` Paul Jarc
2000-10-19 0:20 ` Rob Browning
2000-10-19 16:05 ` Paul Jarc
2000-10-19 23:29 ` Rob Browning
2000-10-20 0:03 ` Paul Jarc
2000-10-20 9:21 ` Kai Großjohann [this message]
2000-10-20 15:27 ` Paul Jarc
2000-10-20 21:08 ` Kai Großjohann
2000-10-20 21:17 ` Paul Jarc
2000-10-20 21:45 ` Kai Großjohann
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=vafg0lr50lm.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=ding@gnus.org \
/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).