Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-devel@gnu.org
Cc: ding@gnus.org
Subject: Re: Gnus cleanup
Date: Sat, 13 Feb 2016 09:57:42 +0800	[thread overview]
Message-ID: <877fi9qsmh.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87fuwyy302.fsf@gnus.org>

Lars Ingebrigtsen <larsi@gnus.org> writes:

[...]

> But please do submit bug reports if this all blows up.

I just pulled and remade Emacs, and when I started Gnus, all my nnimap
groups were displayed and asterisked (nntp was fine). Checking new news
just zips along and tells me everything's fine, no news.

Manually entering each group restores the correct marks to the group,
and after that they work fine. I've got an awful lot of groups, though,
and I wonder if there isn't a way to do this all in one fell swoop.

I'm only assuming this happened because of the cleanups, but I think
it's a reasonable assumption to make!

Eric




  parent reply	other threads:[~2016-02-13  1:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-09  4:13 Lars Ingebrigtsen
2016-02-09  8:35 ` Michael Albinus
2016-02-09  8:35 ` Eric S Fraga
2016-02-09 11:42 ` Malcolm Purvis
2016-02-09 15:30 ` Stefan Monnier
2016-02-09 23:08   ` Lars Ingebrigtsen
2016-02-10  0:50 ` Greg Troxel
2016-02-12  4:19 ` Lars Ingebrigtsen
2016-02-13  0:22   ` Frank Haun
2016-02-13  1:57   ` Eric Abrahamsen [this message]
2016-02-13  3:17     ` Eric Abrahamsen
2016-02-13  3:43       ` Lars Ingebrigtsen
2016-02-13  4:26         ` Eric Abrahamsen
2016-02-13  4:59           ` Lars Ingebrigtsen
2016-02-13 12:00   ` Frank Haun
2016-02-13 15:37     ` Richard Stallman
2016-02-14  2:35     ` Lars Ingebrigtsen
2016-02-14  3:13       ` Adam Sjøgren
2016-02-14 13:12       ` Frank Haun
2016-02-17 21:10       ` Frank Haun
2016-02-18 12:29         ` Frank Haun
2016-03-07 13:52   ` Ted Zlatanov

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=877fi9qsmh.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=ding@gnus.org \
    --cc=emacs-devel@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).