Gnus development mailing list
 help / color / mirror / Atom feed
From: Joe Wells <jbw@cs.bu.edu>
Subject: random questions mostly about Gnus configuration variables
Date: 30 Jun 1996 00:48:59 -0400	[thread overview]
Message-ID: <xnj4tntdhhg.fsf@csb.bu.edu> (raw)

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?

2.  What is gnus-simplify-ignored-prefixes used by?  The doc string is
    unclear.

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?

4.  What in the world does gnus-group-use-permanent-levels do?  The doc
    string is utterly baffling.  What does it mean by "once you set a
    level"?

5.  How do gnus-auto-subscribed-groups, gnus-options-subscribe, and
    gnus-options-not-subscribe interact?

6.  What is the difference between nil and 'some for
    gnus-read-active-file?

7.  Why did I see the message "Loading hexl" while Gnus was fetching
    headers for a group?  What does Gnus use "hexl" for?

8.  What is "~/Mail/drafts" for?

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?

-- 
Joe Wells <jbw@cs.bu.edu>


             reply	other threads:[~1996-06-30  4:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-06-30  4:48 Joe Wells [this message]
1996-06-30  6:54 ` Kai Grossjohann
1996-06-30 18:45 ` Lars Magne Ingebrigtsen
1996-06-30 20:16 ` Sudish Joseph

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=xnj4tntdhhg.fsf@csb.bu.edu \
    --to=jbw@cs.bu.edu \
    /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).