Re: gnorb can't find moved messages

[Eric Abrahamsen <eric@ericabrahamsen.net>]

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> Bob Newell <bobnewell@bobnewell.net> writes:
>
>> This problem also arose for me when I very first started to
>> use Gnorb, and also surprised me as I thought the registry
>> would act as a sort of invariant pointer. However, it didn't.
>
> Thanks to both of you -- it looks to me like the problem is in
> `gnorb-follow-gnus-link', not the registry. I've noticed that sometimes
> if you follow Gnus message links, you get into a Summary buffer that
> includes a bogus (None) message. Usually nothing happens with that, but
> in this case it looks like Gnorb tries to start a reply to that bogus
> message.
>
> In my brief testing, it only happens the first time you try it. After
> the first time Gnorb correctly finds the moved message, and starts a
> reply to it. I have no idea why, I assume some caching is going on.
> Anyway, I will try to fix `gnorb-follow-gnus-link' so it doesn't do
> that.

Okay, it looks like I'd left behind some bits of an earlier attempt at
caching that should have been deleted. I've cleaned that out and bumped
the version; it works for me now.

Give it a shot if you have time!

Eric