From: Andrew Cohen <cohen@andy.bu.edu>
To: ding@gnus.org
Subject: Re: This bug is killing me!
Date: Wed, 31 Aug 2011 16:05:35 -0400 [thread overview]
Message-ID: <87ippdwdm8.fsf@andy.bu.edu> (raw)
In-Reply-To: <m2liu9icp1.fsf@boostpro.com>
>>>>> "Dave" == Dave Abrahams <dave@boostpro.com> writes:
Dave> Thanks for your work on this. It looks like a fairly low-risk
Dave> change, so I'll try it out. And maybe it's a necessary bug
Dave> fix for other reasons, but still... it seems like a function
Dave> (gnus-summary-rescan-group) whose documentation says it exits
Dave> the group and re-enters it should be written to do exactly
Dave> that. Am I missing something?
I can't say for sure. The function does indeed exit the group and
re-enter, but in between it checks for message updates (which is the
'rescan' bit). This checking is significantly different from what you
would get just by hitting 'g' in the *Group* buffer (aside from the
trivial difference that it acts only on the current group). Why exactly
its a different function I can't answer, but it is significantly more
aggressive in what information about the group it tries to rescan.
The specific bug you reported should be fixed by my change---that is,
change a mark, execute 'M-g', and have the new mark persist. The issue
was just that the marks weren't being propagated to the backend (due to
a slightly subtle chain of events). The other issues that have been
reported in this thread may or may not be affected; I can't say because
I can't reproduce them (unlike the original bug report you made which
was easy to reproduce).
next prev parent reply other threads:[~2011-08-31 20:05 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-29 21:51 Dave Abrahams
2011-08-30 7:01 ` Tassilo Horn
2011-08-30 9:27 ` Robert Pluim
2011-08-30 10:12 ` Tassilo Horn
2011-08-30 9:33 ` [Workaround/Solved] " Dave Abrahams
2011-08-30 10:18 ` Tassilo Horn
2011-08-30 10:33 ` Dave Abrahams
2011-08-30 11:20 ` Tassilo Horn
2011-08-30 18:09 ` Dave Abrahams
2011-08-30 18:17 ` Tassilo Horn
2011-09-10 21:59 ` Lars Magne Ingebrigtsen
2011-08-30 10:39 ` Dave Abrahams
2011-08-30 11:50 ` Tassilo Horn
2011-08-30 18:40 ` Dave Abrahams
2011-08-30 15:04 ` James Cloos
2011-08-30 19:02 ` Dave Abrahams
2011-08-30 19:19 ` Tassilo Horn
2011-08-30 19:53 ` Dave Abrahams
2011-08-30 22:07 ` [The saga continues...] " Dave Abrahams
2011-09-10 22:01 ` Lars Magne Ingebrigtsen
2011-08-30 21:36 ` [Workaround/Solved] " James Cloos
2011-08-31 6:40 ` Dave Abrahams
2011-08-31 7:51 ` Tassilo Horn
2011-08-31 8:27 ` James Cloos
2011-08-31 16:51 ` Andrew Cohen
2011-08-31 19:49 ` Dave Abrahams
2011-08-31 20:05 ` Andrew Cohen [this message]
2011-09-10 22:01 ` Lars Magne Ingebrigtsen
2011-09-10 22:12 ` Andrew Cohen
2011-09-10 22:11 ` Lars Magne Ingebrigtsen
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=87ippdwdm8.fsf@andy.bu.edu \
--to=cohen@andy.bu.edu \
--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).