[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#20319: nnoo.el not properly restoring back end server state

From: Alain Schneble
Subject: bug#20319: nnoo.el not properly restoring back end server state
Date: Thu, 26 Jan 2017 20:55:33 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (windows-nt)

Lars Ingebrigtsen <address@hidden> writes:

> Sorry for the late response; due to a misunderstanding the Gnus bug
> reports went to a part of the bug tracker I wasn't checking.

No problem at all.  Thanks for bringing this up.

> Alain Schneble <address@hidden> writes:
>> Anyway, evaluating nnoo-state-alist again shows that server's B state
>> would still be available but is not found because it's listed before nil
>> server's data:
>> => (... (nntp nil ("B" (nntp-address . "news.gnus.org") ...) (nil 
>> (nntp-address) ...)) ...)
>> IIUC, this behavior is wrong.
>> Also, I do not understand why nil server's data is stored (re-pushed)
>> onto the nnoo-state-alist by nnoo-push-server at all.  My understanding
>> is that nil server's data shall be immutable once it's been initialized.
>> But I might be wrong.  What's the use case of re-pushing nil server's data?
> I think you're right, but I haven't looked at the code closely.  Could
> you suggest a patch to fix this problem, perhaps?

Sure, I'll arrange a patch.  Please, just give me a few days...


reply via email to

[Prev in Thread] Current Thread [Next in Thread]