Gnus development mailing list
 help / color / mirror / Atom feed
From: bojohan+news@dd.chalmers.se (Johan Bockgård)
To: emacs-devel@gnu.org
Cc: ding@gnus.org
Subject: Re: GNUS bug: Summary line doesn't match article
Date: Sat, 22 Sep 2007 12:04:54 +0200	[thread overview]
Message-ID: <yoijejgrggmx.fsf@gamma02.me.chalmers.se> (raw)
In-Reply-To: <m2y7f0ja7s.fsf@kenny.sha-bang.de>

Sascha Wilde <wilde@sha-bang.de> writes:

> in some Newsgroups (especially those with much unread messages, but
> this might just be an coincidence) while reading a thread I get
> articles displayed, which are totally unrelated and certainly don't
> match the active line in the summary buffer.

A shot in the dark: are those groups "virtual groups"?

-- 
Johan Bockgård

  parent reply	other threads:[~2007-09-22 10:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-21 15:43 Sascha Wilde
2007-09-21 15:44 ` Sascha Wilde
2007-09-22 10:04 ` Johan Bockgård [this message]
2007-09-22 18:32   ` Sascha Wilde
2007-09-22 19:11     ` Nelson Ferreira
2007-09-24 12:47       ` Sascha Wilde
2007-09-24 15:03         ` Manoj Srivastava
2007-09-23  2:45 ` Dave Goldberg

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=yoijejgrggmx.fsf@gamma02.me.chalmers.se \
    --to=bojohan+news@dd.chalmers.se \
    --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).