From: Felix Lee <flee@teleport.com>
Cc: ding@gnus.org
Subject: Re: nnextern.. backend??
Date: Mon, 27 Oct 1997 11:55:53 -0800 [thread overview]
Message-ID: <199710271954.LAA24992@smtp2.teleport.com> (raw)
In-Reply-To: Your message of 27 Oct 1997 07:50:02 +0100. <ks90vfg0o5.fsf@telelogic.se>
> Would it be possible to have a backend that can execute an external
> (to gnus) program/lisp code when getting articles and posting?
if you can make your external program talk nntp protocol,
you can use nntp.el by setting the server's
nntp-open-connection-function to a function like this:
(defvar nntp-my-program '("sloop" "-p" "-d" "-q" "bach"))
(defun nntp-open-my-program (buffer)
(save-excursion
(set-buffer buffer)
(erase-buffer))
(apply 'start-process "nntpd" buffer nntp-my-program))
(this is what I'm doing in my first try at a compressed
reader protocol.)
--
next prev parent reply other threads:[~1997-10-27 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-27 6:50 Andy Eskilsson
1997-10-27 19:55 ` Felix Lee [this message]
1997-10-28 8:04 ` Andy Eskilsson
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=199710271954.LAA24992@smtp2.teleport.com \
--to=flee@teleport.com \
--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).