Gnus development mailing list
 help / color / mirror / Atom feed
From: jenia.ivlev@gmail.com (jenia.ivlev)
To: ding@gnus.org
Subject: Re: How do you use gnus? really.
Date: Tue, 16 Sep 2014 10:15:49 -0400	[thread overview]
Message-ID: <8761gnps6i.fsf@gmail.com> (raw)
In-Reply-To: <87egvexzzn.fsf@topper.koldfront.dk>


Thanks a lot. I tried doing:
     ;; Keep enough entries to have a good hit rate when referring to an
     ;; article using the registry.  Use long group names so that Gnus
     ;; knows where the article is.
     (setq gnus-registry-max-entries 2500)
     
     (gnus-registry-initialize)
     
     (setq gnus-refer-article-method
           '(current
             (nnregistry)
             (nnweb "gmane" (nnweb-type gmane))))


Its from "9.18.2 Fetching by Message-ID Using the Registry" from GNUS'
manual.

After sending this message, Ill see if it work or not.





  reply	other threads:[~2014-09-16 14:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-13 18:34 jenia.ivlev
2014-09-14  6:29 ` Steinar Bang
2014-09-14 10:13 ` Adam Sjøgren
2014-09-14 10:23   ` Adam Sjøgren
2014-09-16 14:15     ` jenia.ivlev [this message]
2014-09-16 20:55       ` jenia.ivlev
2014-09-17  8:39         ` Eric S Fraga

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=8761gnps6i.fsf@gmail.com \
    --to=jenia.ivlev@gmail.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).