Re: Messages saved in reverse order
Stephen Casner <[email protected]>
| Newsgroups | gmane.mail.pine.general |
|---|---|
| Message-ID | <[email protected]> |
On Tue, 6 Jun 2006, Steve Hubert wrote:
> Without thinking too much let me suggest that you take a look at the
> hidden config feature save-aggregates-copy-sequence. Does that explain it?
That string is not present in my .pinerc.
I did figure out what discriminates the two behaviors. If I have any
deleted attachments, then save() needs to use its special handling
clause. That is the one that works correctly and more quickly!
The case (or at least, a case) where the messages all came out in
reverse order was where I had done a numerical selection contiguous
from message 1. This winds up going through imap_proxycopy() and
thence imap_seq_exec() where the loop goes backwards. In this latter
behavior, func is imap_seq_exec_append which winds up calling
pine_mail_append_full, so it's not doing a simple copy, it's doing
append, which may be why this latter behaviour is counterintuitively
slower.
In any case, it seems to me that the backwards loop must be a bug if
the operation that the loop can perform is to append a message and not
just mark something.
-- Steve
_______________________________________________
Pine-info mailing list
[email protected]
http://mailman1.u.washington.edu/mailman/listinfo/pine-info