From: "Ted Zlatanov" <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: IMAP article move
Date: 25 Feb 2005 15:04:12 -0500 [thread overview]
Message-ID: <4nzmxsbe4j.fsf@lifelogs.com> (raw)
In-Reply-To: <crulql$s14$1@sea.gmane.org> (David Abrahams's message of "Mon, 10 Jan 2005 14:41:30 -0500")
On Mon, 10 Jan 2005, dave@boost-consulting.com wrote:
> The thing that seems to hurt usability the most for me is that Gnus
> rebuilds the summary buffer after each message is moved in a
> multiple-message move.
I see where this happens in gnus-sum.el. Let's give the change I just
made, which eliminates the extra IMAP FETCH, a few days to settle
down, and then I can look at optimizing this summary buffer rebuild
process. Let me know if you notice a performance boost.
If anyone knows why this code is called for every article
move/copy/crosspost:
(set-buffer gnus-summary-buffer)
(gnus-summary-goto-subject article)
in gnus-sum.el, I would appreciate the explanation. I don't know all
the subtleties of the Gnus internals. It seems like it would be
better to either call this just once, after the end of the (while
articles...) loop, or at least every N articles.
Ted
next prev parent reply other threads:[~2005-02-25 20:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-08 19:19 Ted Zlatanov
2004-11-08 20:50 ` Raymond Scholz
2004-11-08 21:15 ` Simon Josefsson
2004-11-09 22:00 ` Ted Zlatanov
2004-11-09 22:06 ` Simon Josefsson
2005-02-25 19:59 ` IMAP article move optimization! (was: IMAP article move) Ted Zlatanov
2005-02-28 0:00 ` IMAP article move optimization! Katsumi Yamaoka
2005-02-28 15:11 ` Ted Zlatanov
2005-03-01 0:37 ` Katsumi Yamaoka
2005-03-01 16:26 ` Ted Zlatanov
2005-03-01 16:51 ` Simon Josefsson
2005-03-03 18:04 ` Ted Zlatanov
2005-03-02 0:39 ` Katsumi Yamaoka
2005-01-10 19:41 ` IMAP article move David Abrahams
2005-02-25 20:04 ` Ted Zlatanov [this message]
2005-03-03 18:05 ` Ted Zlatanov
2005-03-03 19:09 ` David Abrahams
2005-03-04 16:10 ` Ted Zlatanov
2005-03-21 9:32 ` David Abrahams
2005-03-22 19:14 ` Ted Zlatanov
2005-03-22 22:09 ` Simon Josefsson
2005-03-23 19:46 ` Ted Zlatanov
2005-01-11 9:16 ` Bjørn Mork
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=4nzmxsbe4j.fsf@lifelogs.com \
--to=tzz@lifelogs.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).