Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Cc: ding@gnus.org
Subject: Re: Slrnpull
Date: 02 Apr 2001 22:42:20 -0700	[thread overview]
Message-ID: <m34rw6sfoq.fsf@gnus.cvs.983032537> (raw)
In-Reply-To: <87ofufhpi4.fsf@inanna.rimspace.net> (Daniel Pittman's message of "02 Apr 2001 14:52:51 +1000")

Daniel Pittman <daniel@rimspace.net> writes:

[...]

> > The slrnpull docs say it doesn't but it also says leafnode doesn't. 
> 
> It's wrong. Leafnode /is/ an NNTP server. I use it daily to do news on
> my disconnected laptop and my small 23/7 home site.

Turns out it was an over ambitious interpretation from memory on my
part:
>From slrnpull README
[...]
   There are several other ``sucking'' programs available that perform a
   similar function as slrnpull.  The best known are `leafnode' and
   `suck'.  All of them, with the exception of `leafnode' require the
   user to run a newsserver program such as INN or CNEWS.  Like
   `leafnode', slrnpull does not require a newsserver.
[..]

> Works great. I would not hesitate to recommend it and can offer help
> setting it up, should you require some.

Thanks for the offer.  The reason I've steered clear of leafnode, is
I've noticed many comments about it using some kind of heuristics to
determine what groups to get etc.

I don't really want heuristics.  I want to tell an app exactly what to
get and have it get all messages from my list, always.

Is that easily done with leafnode?  I had hoped it would be with
slrnpull, and maybe it is.  I have the downloading working well now.
Very simple and straightforward.  I just had a dumb typo in my code.

I still haven't gotten into trying out posting. I've had some tips
on that though.



  reply	other threads:[~2001-04-03  5:42 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-02  3:11 Slrnpull Harry Putnam
2001-04-02  4:52 ` Slrnpull Daniel Pittman
2001-04-03  5:42   ` Harry Putnam [this message]
2001-04-03  7:16     ` Slrnpull Kai Großjohann
2001-04-03 14:46       ` Slrnpull Laura Conrad
2001-04-03 23:42     ` Slrnpull Daniel Pittman
2001-04-04  3:35       ` Slrnpull Harry Putnam
2001-04-04  4:23         ` Slrnpull Daniel Pittman
2001-04-03 19:51   ` Slrnpull Colin Walters
2001-04-03 21:13     ` Slrnpull Stainless Steel Rat
2001-04-04  0:00       ` Slrnpull Colin Walters
2001-04-04  1:54         ` Slrnpull Stainless Steel Rat
2001-04-04  3:45           ` Slrnpull Harry Putnam
2001-04-04 16:02             ` Slrnpull Stainless Steel Rat
2001-04-04 17:10               ` Slrnpull Harry Putnam
2001-04-04  2:08     ` Slrnpull Daniel Pittman
2001-04-11 16:53       ` Slrnpull Colin Walters
2001-04-05  8:03     ` Slrnpull Kai Großjohann
2001-04-02  8:47 ` Slrnpull Anssi Saari
2001-04-02 11:08   ` Slrnpull Kai Großjohann
2001-04-02 14:44   ` Slrnpull Harry Putnam
2001-04-02 16:02     ` Slrnpull Kevin Falcone
2001-04-03  2:42       ` Slrnpull Harry Putnam
2001-04-03  3:33         ` Slrnpull Kevin Falcone
2001-04-03  6:38           ` Slrnpull Harry Putnam
2001-04-02 20:17     ` Slrnpull 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=m34rw6sfoq.fsf@gnus.cvs.983032537 \
    --to=reader@newsguy.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).