Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: gnus uses a cache?  And how it affects mairix searches...
Date: Wed, 22 Oct 2014 15:47:53 +0800	[thread overview]
Message-ID: <87r3y0a6l2.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <877fzu1ehs.fsf@ericabrahamsen.net>

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

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> Dan Christensen <jdc@uwo.ca> writes:
>
>> Dan Christensen <jdc@uwo.ca> writes:
>>
>>> [Sorry to hijack the thread.  Subject adjusted.]
>>>
>>> James Cloos <cloos@jhcloos.com> writes:
>>>
>>>> There is some caching of articles w/in a given session, but nothing I'm
>>>> aware of which would survive a restart.
>>>
>>> Since upgrading Ubuntu and Gnus, I've noticed that the results of
>>> nnmairix searches infiltrate subsequent search results.  More precisely,
>>> the second time I do a search, the summary buffer looks correct, but for
>>> some of the articles, when I select them the *Article* buffer shows the
>>> articles from the previous search.  The third search may show article
>>> buffers from the first or second search (or both).
>>>
>>> My search results are stored in a local imap folder (dovecot), and I
>>> have verified that on disk the correct articles are stored.  I have also
>>> verified that if I connect to dovecot via telnet, it displays the
>>> correct article bodies.  I am not using the agent (as far as I know).
>>>
>>> I have also tried various nnmairix keystrokes to redo searches, etc,
>>> and none of them helped.
>>>
>>> Any idea why this is happening?  nnmairix used to work beautifully for
>>> me.
>>>
>>> Dan
>>
>> I finally figured this out.  Setting gnus-keep-backlog to nil solved
>> the problem.  It turns out that by default, gnus caches the most recent
>> 20 articles you have viewed, rather than contacting the server again.
>> This is true even if you exit and reenter a summary buffer.
>>
>> Maybe nnmairix should remove articles from this cache when it creates
>> a search folder?  Or bind this variable to nil in nnmairix groups?
>
> Hmm, I may have seen this in nnir groups, as well. At least, I've (only
> once or twice) had a similar situation: selecting articles in an nnir
> search summary buffer, and seeing article bodies from the last search. I
> can only assume it's the same problem...

Just had it again! See attachment -- the article body shown when
selecting one summary line actually belongs to a different summary line.
This time it seems fairly reproducible (and is messing with
Gnorb-related stuff) so I'll see if I figure it out, starting with
setting gnus-keep-backlog to 0.


[-- Attachment #2: nnir.png --]
[-- Type: image/png, Size: 80333 bytes --]

  reply	other threads:[~2014-10-22  7:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-06 22:36 gnus uses a cache? Sharon Kimble
2014-09-07 11:40 ` Adam Sjøgren
2014-09-07 14:22 ` James Cloos
2014-09-08  1:26   ` gnus uses a cache? And how it affects mairix searches Dan Christensen
2014-10-20 22:51     ` Dan Christensen
2014-10-20 23:57       ` Eric Abrahamsen
2014-10-22  7:47         ` Eric Abrahamsen [this message]
2014-10-22  8:30           ` Eric Abrahamsen
2014-10-23  6:59             ` Alan Schmitt
2014-10-24 15:13       ` Eric Abrahamsen
2014-10-28 14:32         ` Dan Christensen
2014-10-28 17:52           ` Andreas Schwab
2014-11-12  1:45             ` Eric Abrahamsen
2014-11-12  3:08               ` Eric Abrahamsen
2014-11-12 21:28                 ` Dan Christensen
2014-11-13  0:26                   ` Eric Abrahamsen
2014-11-16  1:00                     ` Dan Christensen
2014-11-16  3:36                       ` Eric Abrahamsen
2015-01-27  5:03                         ` Lars Ingebrigtsen
2014-09-24 15:35 ` gnus uses a cache? Ted Zlatanov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r3y0a6l2.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).