From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Help! "Can't select group"
Date: Fri, 17 Feb 2012 11:03:36 -0500 [thread overview]
Message-ID: <877gzlzbtz.fsf@lifelogs.com> (raw)
In-Reply-To: <m2booy0xad.fsf@boostpro.com> (Dave Abrahams's message of "Thu, 16 Feb 2012 20:49:30 -1000")
On Thu, 16 Feb 2012 20:49:30 -1000 Dave Abrahams <dave@boostpro.com> wrote:
DA> on Tue Feb 14 2012, Lars Ingebrigtsen <larsi-AT-gnus.org> wrote:
>> Dave Abrahams <dave@boostpro.com> writes:
>>
>>> Something in my setup keeps getting corrupted, I think, but I can't tell
>>> what. When I try to enter gmane.comp.file-systems.zero-install.devel, I
>>> get "Can't select group."
>>
>> This is probably fixed now in Ma Gnus. It was due to buggy `unexist'
>> handling.
DA> It's still broken for me after an update from Git and an attempt to wipe
DA> out all information in my .newsrc, etc., that refers to the group.
Any chance that, like me, you are using gnus-sync or something else to
sync marks? That could be pulling the unexist marks back until you
clean them *and* force an overwrite.
Try the following, adapted from `gnus-clean-old-newsrc' to clean
unconditionally and to tell you it's doing so. You may want to adapt it
to just do your problematic NNTP groups.
#+begin_src lisp
;; Remove old `exist' marks from old nnimap groups.
(dolist (info (cdr gnus-newsrc-alist))
(let ((exist (assoc 'unexist (gnus-info-marks info))))
(when exist
(message "Cleaning unexist marks from group %s" (car info))
(gnus-info-set-marks
info (delete exist (gnus-info-marks info))))))
#+end_src
Ted
prev parent reply other threads:[~2012-02-17 16:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-14 20:18 Dave Abrahams
2012-02-14 23:32 ` Eric S Fraga
2012-02-15 9:17 ` Lars Ingebrigtsen
2012-02-15 11:07 ` Eric S Fraga
2012-02-16 17:17 ` Dave Abrahams
2012-02-20 7:34 ` Lars Ingebrigtsen
2012-02-21 1:43 ` Dave Abrahams
2012-02-21 21:24 ` Ted Zlatanov
2012-02-17 6:49 ` Dave Abrahams
2012-02-17 16:03 ` Ted Zlatanov [this message]
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=877gzlzbtz.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).