nnimap and gnus-use-cache

nnimap and gnus-use-cache

[Julien Danjou]

[-- Attachment #1: Type: text/plain, Size: 802 bytes --]

Hi,

I had gnus-use-cache set to t in my .gnus.el.

I discovered that setting the important mark would cache the article.
Useful!

But that triggers a bug: when accessing old articles in a group,
sometimes, say I want to read a random article so I press RET…

…but Gnus ends opening another article, one which is cached and
important. I have to delete the cache so I can read the article I want.
If I don't, I cannot open this article, Gnus just keep going back to the
cached article (which is totally unrelated).

I've set back gnus-use-cache to its default value, passive, so I don't
have this behaviour anymore, but well, that can bother other people. :)

That maybe an UID problem, I've no clue.

-- 
Julien Danjou
// ᐰ <julien@danjou.info>   http://julien.danjou.info

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

Re: nnimap and gnus-use-cache

[Steinar Bang]

>>>>> Julien Danjou <julien@danjou.info>:

> But that triggers a bug: when accessing old articles in a group,
> sometimes, say I want to read a random article so I press RET…

> …but Gnus ends opening another article, one which is cached and
> important. I have to delete the cache so I can read the article I want.
> If I don't, I cannot open this article, Gnus just keep going back to the
> cached article (which is totally unrelated).

Ah!  That happened to me the other day, as well.

Re: nnimap and gnus-use-cache

[Lars Magne Ingebrigtsen]

Julien Danjou <julien@danjou.info> writes:

> …but Gnus ends opening another article, one which is cached and
> important. I have to delete the cache so I can read the article I want.
> If I don't, I cannot open this article, Gnus just keep going back to the
> cached article (which is totally unrelated).

Wow!  How bizarre.  But I'm able to reproduce it.  

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: nnimap and gnus-use-cache

[Lars Magne Ingebrigtsen]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Wow!  How bizarre.  But I'm able to reproduce it.  

That was a bug that's been there forever and ever, but would only be
triggered by backends that don't support NOV, like nnimap now.

Fixed and pushed.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: nnimap and gnus-use-cache

[Steinar Bang]

>>>>> Lars Magne Ingebrigtsen <larsi@gnus.org>:

> That was a bug that's been there forever and ever, but would only be
> triggered by backends that don't support NOV, like nnimap now.

> Fixed and pushed.

Wasn't the one I saw, then.  What I saw was something similar when using
the agent.  Somehow one article was replaced with its neighbour.  The
two articles in ~/News/agent/nnimap/privat/folder/ were identical.

What I did was delete the wrong article in the agent did, and then read
the article again and the correct one showed up.

I'm using this setting to save articles in the agent as I read them:
 (add-hook 'gnus-select-article-hook 'gnus-agent-fetch-selected-article)

Re: nnimap and gnus-use-cache

[Lars Magne Ingebrigtsen]

Steinar Bang <sb@dod.no> writes:

> Wasn't the one I saw, then.  What I saw was something similar when using
> the agent.  Somehow one article was replaced with its neighbour.  The
> two articles in ~/News/agent/nnimap/privat/folder/ were identical.

Right.  Sounds like a different problem.  This bug was that several
articles returned the same number when you evaled

  (gnus-summary-article-number)

on a summary line.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: nnimap and gnus-use-cache

[Steinar Bang]

>>>>> Lars Magne Ingebrigtsen <larsi@gnus.org>:

> Steinar Bang <sb@dod.no> writes:
>> Wasn't the one I saw, then.  What I saw was something similar when using
>> the agent.  Somehow one article was replaced with its neighbour.  The
>> two articles in ~/News/agent/nnimap/privat/folder/ were identical.

> Right.  Sounds like a different problem.  This bug was that several
> articles returned the same number when you evaled

>   (gnus-summary-article-number)

> on a summary line.

What happened to me now, was that an agent article (newesst date and
biggest article number) was replaced by the contents of the .overview (a
slightly older version of the .overview, I think).

This was before my latest pull, and I have no consistent way of
reproducing this.