From: Damien Leone <damien.leone@fensalir.fr>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Adding backward synchronization for Maildir sources
Date: Tue, 20 Jul 2010 11:39:41 +0200 [thread overview]
Message-ID: <1279618205-sup-993@mailer> (raw)
In-Reply-To: <1279492496-sup-3638@ezyang>
[-- Attachment #1.1: Type: text/plain, Size: 1963 bytes --]
Sup Edward,
Thank you for your feedback!
Excerpts from Edward Z. Yang's message of Mon Jul 19 00:46:33 +0200 2010:
> It makes Sup very crashy and there's some strange behavior. This is probably
> the sixth time I'm composing this message (yeah, haven't learned my
> lesson.) In more detail...
I'm impressed, I never experienced such crashes, it is quite stable
here but I use only very basic hooks.
> * Backwards syncing appears to make old deleted mail show up again; I'm not
> sure if it's because touching the Maildir causes Sup to pick up on deleted
> tags again or something, but I had to go back and delete lots of deleted mail.
Hmm, strange, do you use the latest commits of the branch? I pushed a
fix for deleted mails about 10 days ago.
The mails that show up again don't have the deleted flag at all?
> * When Sup is deleting messages, it is /extremely/ unsafe to iterate over
> a list of all messages in the index and query them for info: the threading means
> that any given message might not exist anymore. I had a hook that kept triggering
> this bug, and earlier on in the process drawing functions would also frequently
> Nil error. This is probably under-tested codepaths in Sup that we should track
> down; unfortunately I didn't have the presence of mind to record traces until
> later (and the ones I got all look like my hooks fault).
I did not test the code with hooks, what do you suggest for this one?
> * In a similar vein, while messages are going away, '@' will occasionally return
> no messages (pressing again usually fixes it). Messages that are labelled inbox
> will show up in 'U', but not in the inbox view without a Sup restart.
I never use this keybinding but indeed I noticed that pressing '@' two
times in a row was not showing anything.
I will try to track down these bugs.
Thanks again!
Cheers,
--
Damien Leone <damien.leone@fensalir.fr>
Web: http://dleone.fensalir.fr/
GPG: 0x82EB4DDF
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2010-07-20 9:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-09 16:44 Damien Leone
2010-07-09 16:56 ` Edward Z. Yang
2010-07-09 17:14 ` Damien Leone
2010-07-09 19:46 ` Edward Z. Yang
2010-07-17 12:55 ` Damien Leone
2010-07-17 17:05 ` Ben Walton
2010-07-17 17:26 ` Damien Leone
2010-07-18 11:19 ` Tero Tilus
2010-07-18 22:46 ` Edward Z. Yang
2010-07-20 9:39 ` Damien Leone [this message]
2010-07-21 0:44 ` Edward Z. Yang
2010-07-21 8:52 ` Damien Leone
2010-07-21 8:54 ` Damien Leone
2010-07-18 22:50 ` Edward Z. Yang
2010-07-20 9:45 ` Damien Leone
2010-07-18 22:57 ` Edward Z. Yang
2010-07-24 21:30 ` Rich Lane
2010-07-25 22:25 ` Edward Z. Yang
2011-03-13 16:41 ` Damien Leone
2011-10-27 12:34 ` Justin Mazzi
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=1279618205-sup-993@mailer \
--to=damien.leone@fensalir.fr \
--cc=sup-devel@rubyforge.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