From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/7048 Path: main.gmane.org!not-for-mail From: Sudish Joseph Newsgroups: gmane.emacs.gnus.general Subject: Re: random questions mostly about Gnus configuration variables Date: 30 Jun 1996 16:16:07 -0400 Sender: sj@mindspring.com Message-ID: References: NNTP-Posting-Host: coloc-standby.netfonds.no X-Trace: main.gmane.org 1035147416 5710 80.91.224.250 (20 Oct 2002 20:56:56 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 20:56:56 +0000 (UTC) Return-Path: ding-request@ifi.uio.no Original-Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by deanna.miranova.com (8.7.5/8.6.9) with SMTP id NAA29080 for ; Sun, 30 Jun 1996 13:53:50 -0700 Original-Received: from atreides.erehwon.org (sj@user-168-121-167-78.dialup.mindspring.com [168.121.167.78]) by ifi.uio.no with ESMTP (8.6.11/ifi2.4) id for ; Sun, 30 Jun 1996 22:12:28 +0200 Original-Received: (from sj@localhost) by atreides.erehwon.org (8.7.5/8.7.3) id QAA00239; Sun, 30 Jun 1996 16:16:08 -0400 Original-To: ding@ifi.uio.no In-Reply-To: Joe Wells's message of 30 Jun 1996 00:48:59 -0400 Original-Lines: 53 X-Mailer: Gnus v5.2.25/XEmacs 19.14 Xref: main.gmane.org gmane.emacs.gnus.general:7048 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:7048 In article , Joe Wells writes: > Hi, Gnusians, > Here are some random questions mostly about Gnus configuration variables: > 1. The doc string ("C-h v") of gnus-fetch-old-headers is unclear. The > doc string seems to imply that Gnus will scan the "references" headers > of the articles and then request the headers of the referred articles. > But in fact, setting this variable non-nil seems to make Gnus blindly > fetch all of the headers in the newsgroup. What really happens? It used to be that setting it to 'some worked like you describe. Did you try this? I no longer use this over PPP. > 2. What is gnus-simplify-ignored-prefixes used by? The doc string is > unclear. The gnus-simplify-* stuff tries to canonicalise subject headers before thy're sorted. For instance "foo (was: bar)" and "foo" would be treated as the same subject. > 3. The doc string of gnus-build-sparse-threads is unclear. What does > this really do? What are the "gaps" to which the doc string refers? I believe they refer to the missing articles in a thread where you might have the 1st and nth descendant. Sort of like fetch-old-headers where the intermediates can't be fecthed, or have already been read. This is from memory, I never used this. Pls. correct me if I'm wrong. > 6. What is the difference between nil and 'some for > gnus-read-active-file? Good question. I don't see why 'some shouldn't be equivalent to nil functionally. They're not equivalent right now from a look at the code--I don't have the enthusiasm to edebug through active file lookups over a PPP link. :-) > 7. Why did I see the message "Loading hexl" while Gnus was fetching > headers for a group? What does Gnus use "hexl" for? QP decoding, apparently. > 9. What are the interactions between the to-address, to-group, and > to-list parameters of a group? What happens if you set more than one > of them? What is the difference between to-address and to-list? I've said way too much on this topic to start on this. :-) If you dig around the archives you should find a longish thread on this topic around Fall last year. -- Sudish