From: Alain Schneble <a.s@realize.ch>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 20319@debbugs.gnu.org
Subject: bug#20319: nnoo.el not properly restoring back end server state
Date: Thu, 26 Jan 2017 20:55:33 +0100 [thread overview]
Message-ID: <867f5hlhoq.fsf@realize.ch> (raw)
In-Reply-To: <877f5hzotn.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 26 Jan 2017 18:57:40 +0100")
Lars Ingebrigtsen <larsi@gnus.org> 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 <a.s@realize.ch> 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...
Alain
next parent reply other threads:[~2017-01-26 19:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86r3rng4gy.fsf@realize.ch>
[not found] ` <877f5hzotn.fsf@gnus.org>
2017-01-26 19:55 ` Alain Schneble [this message]
2018-04-12 21:11 ` bug#20319: nnoo.el not properly restoring back end server state Lars Ingebrigtsen
2019-09-27 0:15 ` Lars Ingebrigtsen
2019-09-29 1:10 ` Eric Abrahamsen
2019-09-29 10:39 ` Lars Ingebrigtsen
2019-10-14 7:29 ` Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=867f5hlhoq.fsf@realize.ch \
--to=a.s@realize.ch \
--cc=20319@debbugs.gnu.org \
--cc=larsi@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).