[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Gnus: Gcc and imap folders
From: |
Tassilo Horn |
Subject: |
Re: Gnus: Gcc and imap folders |
Date: |
Mon, 12 Sep 2016 11:58:10 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) |
Arash Esbati <arash.esbati+ml@gmail.com> writes:
Hi Arash,
> I can't get Gcc and threading work reliably in imap folders. Here an
> example: Incoming mail is shown without parent.
>
> [img]
>
> When I hit `A r', the parent is shown and I get threading:
I can't see your screenshot (I'm ssh-ed into a server) but can it be
that you don't see the parents because you've already read them before?
By default, Gnus won't show old mail. That's controlled by this
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’
| Original value was nil
|
| 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. Setting it to t for groups for a
| server that doesn’t expire articles (such as news.gmane.org),
| leads to very slow summary generation.
|
| You can customize this variable.
`----
> One thing occured to me is that pretty printing of char numbers is
> broken (n/a) -- it looks fine for the same message in my sent-mail
> archive (I Gcc all mails into nnml+archive:sent-mail, see below).
What are "char numbers"?
Bye,
Tassilo