Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: gnus-large-newsgroup for ephemeral groups
Date: Wed, 23 Apr 2003 21:31:23 +0200	[thread overview]
Message-ID: <v94r4pggdw.fsf@marauder.physik.uni-ulm.de> (raw)

Hi,

I've set `gnus-large-newsgroup' to nil.  I see the number of unread
articles in the Group buffer so I can use `42 RET' if I don't want to
see all.  

But when I click on a link like
news://news.gmane.org/gmane.emacs.gnus.general I definitively don't
want to fetch 50000+ headers.

With the following patch, different settings for ephemeral and regular
groups are possible, e.g.

(setq gnus-large-newsgroup nil
      gnus-fetch-old-headers t
      gnus-large-ephemeral-newsgroup 100
      gnus-fetch-old-ephemeral-headers nil)

--8<---------------cut here---------------start------------->8---
--- gnus-group.el.~6.109.~	Fri Apr  4 14:02:08 2003
+++ gnus-group.el	Wed Apr 23 21:24:01 2003
@@ -1996,7 +1996,9 @@
     (if request-only
 	group
       (condition-case ()
-	  (when (gnus-group-read-group t t group select-articles)
+	  (when (let ((gnus-large-newsgroup gnus-large-ephemeral-newsgroup)
+		      (gnus-fetch-old-headers gnus-fetch-old-ephemeral-headers))
+		  (gnus-group-read-group t t group select-articles))
 	    group)
 	;;(error nil)
 	(quit
--8<---------------cut here---------------end--------------->8---

[ defcustom of gnus-large-ephemeral-newsgroup and
gnus-fetch-old-ephemeral-headers missing. ]

Is there a more suitable approach for this problem?

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo--- PGP key available via WWW   http://rsteib.home.pages.de/




             reply	other threads:[~2003-04-23 19:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-23 19:31 Reiner Steib [this message]
2003-04-24 11:43 ` Kai Großjohann
2003-04-24 18:51   ` Reiner Steib

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=v94r4pggdw.fsf@marauder.physik.uni-ulm.de \
    --to=4.uce.03.r.s@nurfuerspam.de \
    --cc=reiner.steib@gmx.de \
    /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).