From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: updating backend marks immediately
Date: Sun, 05 Dec 2010 15:39:54 +0100 [thread overview]
Message-ID: <m3bp509tc5.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87tyj5h17l.fsf@uwo.ca>
Dan Christensen <jdc@uwo.ca> writes:
> And are commands 309 and 310 needed?
[...]
> 10:14:38 309 SELECT "test"
> 10:14:38 310 UID FETCH 1:* FLAGS
It's this code that's being run:
;; Re-activate all groups that have been moved to.
(with-current-buffer gnus-group-buffer
(let ((gnus-group-marked to-groups))
(gnus-group-get-new-news-this-group nil t)))
I think the idea here is that if you move something to a group, that
group's group line should be updated immediately, so you don't have to
wait until the next `g' to find the article. And
`gnus-group-get-new-news-this-group' does the equivalent of `M-g' on the
group, so it's slow.
I'd be fine with just removing that code snippet altogether. Does `B m'
have to update the resulting groups immediately?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2010-12-05 14:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 20:32 Dan Christensen
2010-11-04 20:37 ` Lars Magne Ingebrigtsen
2010-11-09 22:01 ` Ted Zlatanov
2010-11-10 1:13 ` Dan Christensen
2010-11-10 13:16 ` Ted Zlatanov
2010-11-10 21:00 ` Lars Magne Ingebrigtsen
2010-11-12 23:54 ` Dan Christensen
2010-11-14 15:58 ` Lars Magne Ingebrigtsen
2010-11-14 21:47 ` Dan Christensen
2010-11-21 5:31 ` Lars Magne Ingebrigtsen
2010-11-21 5:38 ` Lars Magne Ingebrigtsen
2010-11-22 1:45 ` Dan Christensen
2010-11-22 1:48 ` Lars Magne Ingebrigtsen
2010-11-24 21:39 ` Dan Christensen
2010-11-24 21:46 ` Lars Magne Ingebrigtsen
2010-11-24 22:04 ` Lars Magne Ingebrigtsen
2010-11-25 12:00 ` Steinar Bang
2010-11-25 14:28 ` Lars Magne Ingebrigtsen
2010-11-25 14:40 ` Steinar Bang
2010-11-25 15:28 ` Dan Christensen
2010-12-05 14:39 ` Lars Magne Ingebrigtsen [this message]
2010-12-05 15:22 ` Dan Christensen
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=m3bp509tc5.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--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).