From: prj@po.cwru.edu (Paul Jarc)
Subject: gnus-declare-backend in the manual
Date: Tue, 28 Aug 2001 00:45:45 -0400 [thread overview]
Message-ID: <m366b8u700.fsf@multivac.cwru.edu> (raw)
I think "Hooking New Backends Into Gnus" node of the manual could
mention that the call to gnus-declare-backend belongs in the backend's
.el file. This was a detail I didn't figure out when I started
nnmaildir, and at the time, none of the standard backends used it, so
there was no example to work from. I guess gnus-declare-backend
should appear in the index, too, pointing to this node.
Also, how does one decide which abilities ought to be listed? E.g.,
it seems that 'respool corresponds straightforwardly to
nnchoke-request-{move,accept}-article. But if so, why bother
duplicating this information?
paul
next reply other threads:[~2001-08-28 4:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-28 4:45 Paul Jarc [this message]
2001-09-01 17:08 ` 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=m366b8u700.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
/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).