Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: The Gnus Mailing List <ding@gnus.org>
Subject: Re: gnus-summary-catchup-and-exit not setting marks
Date: Mon, 23 Sep 2002 12:24:57 +0200	[thread overview]
Message-ID: <ilun0q9atqe.fsf@latte.josefsson.org> (raw)
In-Reply-To: <u8zznucv57g.fsf@blackbird-2k.MITRE.ORG> (David S Goldberg's message of "Fri, 20 Sep 2002 15:20:03 -0400")

David S Goldberg <david.goldberg6@verizon.net> writes:

> In some groups, regardless of back end (I have nntp, nnml, nnimap, all
> of which are affected), pressing c, gnus-summary-catchup-and-exit
> doesn't always do the catch up part.  

Is the group buffer updated or not?

I think I have seen this too, but only after `g' after a `c' -- the
catched up messages are back as unread.  This is nnimap.

> In other groups it works fine.  Looking at show-message-log, in the
> groups in which it works, I see a message "Setting marks in ...", in
> the others I don't.  I'm also not positive it's always happening in
> the same groups.  I've looked through group params etc and can't
> find any obvious differences.  If I do the equivalent work of that
> function with M C Z n, then all works as expected.  It almost seems
> like there's a race condition somewhere.  Any advice on how I could
> try to debug this?

If you can reproduce it easily, edebugging `c' is a starting point.




  parent reply	other threads:[~2002-09-23 10:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-20 19:20 David S Goldberg
2002-09-23  9:56 ` Niklas Morberg
2002-09-23 12:51   ` Jinhyok Heo
2002-09-23 10:24 ` Simon Josefsson [this message]
2002-09-23 21:22   ` Clemens Fischer
2002-09-24 11:49     ` Simon Josefsson
2002-09-25  8:56       ` Niklas Morberg
2002-09-25 13:20         ` Simon Josefsson
2002-09-24 15:26     ` David S 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=ilun0q9atqe.fsf@latte.josefsson.org \
    --to=jas@extundo.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).