Re: show read posts

[Tassilo Horn]

Gary Wessle <not@defined.now> writes:

Hi Gary,

> is there a way to go back and read posts which were previously read, I
> don't seem to find them in the summary buffer.

Sure, have a look at:

,----[ `^' in summary buffer ]
| ^ runs the command gnus-summary-refer-parent-article which is an
| interactive compiled Lisp function in `gnus-sum.el'.
| It is bound to ^, A r, A ^, <menu-bar> <Article> <Fetch parent of
| article>.  (gnus-summary-refer-parent-article N)
| 
| Refer parent article N times. If N is negative, go to ancestor -N
| instead.  The difference between N and the number of articles fetched
| is returned.
`----

,----[ `A-T' in summary buffer ]
| A T runs the command gnus-summary-refer-thread which is an interactive
| compiled Lisp function in `gnus-sum.el'.
| It is bound to A T, <menu-bar> <Threads> <Find all messages in
| thread>, <menu-bar> <Article> <Fetch current thread>.
| (gnus-summary-refer-thread &optional LIMIT)
| 
| Fetch all articles in the current thread. If LIMIT (the numerical
| prefix), fetch that many old headers instead of what's specified by
| the `gnus-refer-thread-limit' variable.
`----

and

,----
| A R runs the command gnus-summary-refer-references which is an
| interactive compiled Lisp function in `gnus-sum.el'.
| It is bound to A R, <menu-bar> <Article> <Fetch referenced articles>.
| (gnus-summary-refer-references)
| 
| Fetch all articles mentioned in the References header. Return the
| number of articles fetched.
`----

You could also have a look at the variable

,----[ C-h v gnus-fetch-old-headers RET ]
| gnus-fetch-old-headers is a variable defined in `gnus-sum.el'.
| Its value is some
| 
| Documentation: *Non-nil means that Gnus will try to build threads by
| grabbing old headers.  If an unread article in the group refers to an
| older, already read (or just marked as read) article, the old article
| will not normally be displayed in the Summary buffer.  If this
| variable is t, Gnus will attempt to grab the headers to the old
| articles, and thereby build complete threads.  If it has the value
| `some', all old headers will be fetched but only enough headers to
| connect otherwise loose threads will be displayed.  This variable can
| also be a number.  In that case, no more than that number of old
| headers will be fetched.  If it has the value `invisible', all old
| headers will be fetched, but none will be displayed.
| 
| The server has to support NOV for any of this to work.
| 
| This feature can seriously impact performance it ignores all
| locally cached header entries.
`----


Bye,
Tassilo
-- 
A child of five could understand this! Fetch me a child of five!