From: Lars Ingebrigtsen <larsi@gnus.org>
To: Garjola Dindi <garjola@garjola.net>
Cc: info-gnus-english@gnu.org
Subject: Re: Maybe a bug after df89d6d6dc429e638e425536d1c201b5373f2abd
Date: Sat, 28 Dec 2019 01:50:17 +0100 [thread overview]
Message-ID: <87fth5e0ja.fsf@gnus.org> (raw)
In-Reply-To: <87y2ux8g1z.fsf@pc-117-162.ovh.com> (Garjola Dindi's message of "Sat, 28 Dec 2019 01:11:36 +0100")
Garjola Dindi <garjola@garjola.net> writes:
> I have a strange behaviour with recent versions of gnus (in emacs
> master and branch emacs-27).
>
> When I try to subscribe to a group in the *Browse server buffer*, all
> groups appear with the ’K’ mark and the subscribe command ’u’ does not
> subscribe (the ’K’ still appears and the group is not subscribed).
This was due to a recent change -- whenever a group changed level, it
would put a nil onto gnus-newsrc-alist, thereby making it invalid.
I've now pushed a fix for this to both emacs-27 and the trunk.
> Also, the .newsrc.eld file does not contain anything after the line
> showing the Gnus version number. This means that all existing
> subscriptions are lost after exiting emacs.
Geez! I didn't see that problem -- I just got some extra nil entries at
the start of the gnus-newsrc-alist variable. I hope there's a backup of
the file...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2019-12-28 0:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-28 0:11 Garjola Dindi
2019-12-28 0:26 ` Adam Sjøgren via info-gnus-english
2019-12-28 0:50 ` Lars Ingebrigtsen [this message]
2019-12-28 1:17 ` Adam Sjøgren via info-gnus-english
2019-12-28 1:19 ` Adam Sjøgren via info-gnus-english
2019-12-28 1:29 ` Lars Ingebrigtsen
2019-12-28 7:42 ` Garjola Dindi
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=87fth5e0ja.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=garjola@garjola.net \
--cc=info-gnus-english@gnu.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).