I just upgraded my Gnus to v5.13, using the emacs23 debian lenny
backport.
Since then, I noticed that each time I restart Gnus, my nnimap server is
not agentized anymore. Here is what I see in the Server buffer:
{nnfolder:archive} (closed)
{nntp:} (opened)
{nnimap:} (opened)
I have to re-add agent (J a), but at next start, it is lost again.
My gnus-agent's value is t.
My gnus-secondary-select-methods's value is
((nnimap ""
(nnimap-address "localhost"))
(nntp ""
(nntp-address "localhost")))
Any idea ?
Thanks,
--
Nicolas
Maybe setting gnus-agent via gnus-parameters or topics-parameters, like
(setq gnus-parameters
'(("imap.*\\|nndoc.*" ;; select group with a regexp
(gnus-show-threads nil) ;; set some variable
(gnus-agent t))))
I must say that I encountered problems with imap and gnus-agent set to t,
(deleted messages never going away from the summary buffer)
and I am not the only one, from what I can see in this newsgroup.
So I don't recommend it.
> Nicolas KOWALSKI <ni...@petole.demisel.net> writes:
>
>> I just upgraded my Gnus to v5.13, using the emacs23 debian lenny
>> backport.
>>
>> Since then, I noticed that each time I restart Gnus, my nnimap server is
>> not agentized anymore. Here is what I see in the Server buffer:
> Maybe setting gnus-agent via gnus-parameters or topics-parameters, like
>
> (setq gnus-parameters
> '(("imap.*\\|nndoc.*" ;; select group with a regexp
> (gnus-show-threads nil) ;; set some variable
> (gnus-agent t))))
No, I just tried it, and this does not work.
> I must say that I encountered problems with imap and gnus-agent set to t,
> (deleted messages never going away from the summary buffer)
> and I am not the only one, from what I can see in this newsgroup.
> So I don't recommend it.
But without the agent, I can not see the full thread when a new message
arrives in, even with gnus-fetch-old-headers's value set as t. I find
this annoying.
--
Nicolas