Next: , Previous: , Up: Customizing Threading   [Contents][Index] More Threading


If this variable is nil, no threading will be done, and all of the rest of the variables here will have no effect. Turning threading off will speed group selection up a bit, but it is sure to make reading slower and more awkward.


If non-nil, all threads will be hidden when the summary buffer is generated.

This can also be a predicate specifier (see Predicate Specifiers). Available predicates are gnus-article-unread-p and gnus-article-unseen-p.

Here’s an example:

(setq gnus-thread-hide-subtree
      '(or gnus-article-unread-p

(It’s a pretty nonsensical example, since all unseen articles are also unread, but you get my drift.)


All threads that have a total score (as defined by gnus-thread-score-function) less than this number will be expunged. This variable is nil by default, which means that no threads are expunged.


if you kill a thread and this variable is non-nil, the subtree will be hidden.


Sometimes somebody changes the subject in the middle of a thread. If this variable is non-nil, which is the default, the subject change is ignored. If it is nil, a change in the subject will result in a new thread.


This is a number that says how much each sub-thread should be indented. The default is 4.


Sometimes, particularly with mailing lists, the order in which mails arrive locally is not necessarily the same as the order in which they arrived on the mailing list. Consequently, when sorting sub-threads using the default gnus-thread-sort-by-number, responses can end up appearing before the article to which they are responding to. Setting this variable to an alternate value (e.g., gnus-thread-sort-by-date), in a group’s parameters or in an appropriate hook (e.g., gnus-summary-generate-hook) can produce a more logical sub-thread ordering in such instances.

Next: Low-Level Threading, Previous: Filling In Threads, Up: Customizing Threading   [Contents][Index]