Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: Johan Vromans <jvromans@squirrel.nl>
Cc: ding@gnus.org
Subject: Re: Need help after upgrade
Date: Wed, 18 Jul 2012 09:55:57 -0400	[thread overview]
Message-ID: <87k3y1npg2.fsf@lifelogs.com> (raw)
In-Reply-To: <loom.20120712T082408-41@post.gmane.org> (Johan Vromans's message of "Thu, 12 Jul 2012 07:16:04 +0000 (UTC)")

On Thu, 12 Jul 2012 07:16:04 +0000 (UTC) Johan Vromans <jvromans@squirrel.nl> wrote: 

JV> I've been using Gnus for over ten years, mainly to handle mailing lists.
JV> Using a procmail(-like) filter I deliver mail from mailing lists into a local
JV> news spool and read them with Gnus as nnml groups. So far so good.

JV> Recently I upgraded from Emacs 21.4 to 24.0 and I came across a very annoying
JV> change in behaviour.
...
JV> With the new Emacs/Gnus, I get to see *all* lists, but without new message
JV> information:

JV> [ Gnus -- 0 ]
JV>   [ Mailing lists -- 0 ]
JV>     [ Graphics -- 0 ]
JV>            *: nnml:maillists.gimp-user-list
JV>            *: nnml:maillists.graphics
JV>            *: nnml:maillists.inkscape-user
JV>            *: nnml:maillists.tgif4-announce

JV> (In the real situation, there are about 200 groups spread over several topics.)

Johan, does `M-g' show the correct counts?  If yes, do `M-g' on a topic
and all will be refreshed.  I have something similar happening on Emacs
under Mac OS X, which I thought was a problem with my setup.  So add my
vote to fixing this bug... if it's anything obvious...

Ted



  parent reply	other threads:[~2012-07-18 13:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-12  7:16 Johan Vromans
2012-07-12 17:34 ` Johan Vromans
2012-07-18 13:55 ` Ted Zlatanov [this message]
     [not found]   ` <20487.42252.815283.378741@phoenix.squirrel.nl>
2012-07-19 13:34     ` Ted Zlatanov
2012-07-19 16:01       ` Gijs Hillenius
2012-07-20  7:31       ` Johan Vromans

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=87k3y1npg2.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.org \
    --cc=jvromans@squirrel.nl \
    /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).