From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.204.155.88 with SMTP id r24cs144504bkw; Tue, 20 Jul 2010 17:54:48 -0700 (PDT) Received: by 10.231.184.156 with SMTP id ck28mr6510207ibb.168.1279673686727; Tue, 20 Jul 2010 17:54:46 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id e2si10732076iba.89.2010.07.20.17.54.46; Tue, 20 Jul 2010 17:54:46 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 9F0C419782D9; Tue, 20 Jul 2010 20:54:45 -0400 (EDT) Received: from dmz-mailsec-scanner-6.mit.edu (DMZ-MAILSEC-SCANNER-6.MIT.EDU [18.7.68.35]) by rubyforge.org (Postfix) with ESMTP id CD39F185835E for ; Tue, 20 Jul 2010 20:44:40 -0400 (EDT) X-AuditID: 12074423-b7cb4ae000000a9b-f0-4c4642fa62ba Received: from mailhub-auth-2.mit.edu (MAILHUB-AUTH-2.MIT.EDU [18.7.62.36]) by dmz-mailsec-scanner-6.mit.edu (Symantec Brightmail Gateway) with SMTP id 37.6B.02715.AF2464C4; Tue, 20 Jul 2010 20:44:42 -0400 (EDT) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-2.mit.edu (8.13.8/8.9.2) with ESMTP id o6L0ieLZ007504; Tue, 20 Jul 2010 20:44:40 -0400 Received: from localhost (ool-44c4de0a.dyn.optonline.net [68.196.222.10]) (authenticated bits=0) (User authenticated as ezyang@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id o6L0ic45004157; Tue, 20 Jul 2010 20:44:39 -0400 (EDT) From: "Edward Z. Yang" To: Damien Leone In-reply-to: <1279618205-sup-993@mailer> References: <1278693172-sup-6247@mailer> <1279492496-sup-3638@ezyang> <1279618205-sup-993@mailer> Date: Tue, 20 Jul 2010 20:44:38 -0400 Message-Id: <1279672865-sup-6946@ezyang> User-Agent: Sup/git X-Brightmail-Tracker: AAAAAQCq+Kk= Cc: sup-devel Subject: Re: [sup-devel] Adding backward synchronization for Maildir sources X-BeenThere: sup-devel@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Sup developer discussion List-Id: Sup developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org Excerpts from Damien Leone's message of Tue Jul 20 05:39:41 -0400 2010: > 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. In retrospect, I'm fairly certain the majority of crashes were from user 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? My Sup is running off of f150276f62e263d146fa81ede645b5e90e06a8a1. They don't appear to have the deleted flag, but I didn't look too closely. It's *possible* that a regular synchronization would have picked them up, if they accidentally got dropped from my Sup index but were still inside my Maildir. I suggest not worrying too much about this unless someone else reproduces. > I did not test the code with hooks, what do you suggest for this one? I mentioned this in the id and Nil message; basically, when iterating over all messages messages might disappear, and some hooks need to check if a message is Nil before doing anything to it. > > * 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. It is possible that this is a bug in vanilla Sup. Cheers, Edward _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel