From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.42.229.71 with SMTP id jh7cs183462icb; Wed, 19 Jan 2011 13:48:40 -0800 (PST) Received: by 10.224.11.146 with SMTP id t18mr1123073qat.139.1295473720433; Wed, 19 Jan 2011 13:48:40 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id s14si15276554qcp.7.2011.01.19.13.48.40; Wed, 19 Jan 2011 13:48:40 -0800 (PST) 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; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 01D7218581F3; Wed, 19 Jan 2011 16:48:40 -0500 (EST) Received: from mail-gy0-f178.google.com (mail-gy0-f178.google.com [209.85.160.178]) by rubyforge.org (Postfix) with ESMTP id 679781858361 for ; Wed, 19 Jan 2011 16:10:35 -0500 (EST) Received: by gyh4 with SMTP id 4so573054gyh.23 for ; Wed, 19 Jan 2011 13:10:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:content-type:subject:from:to:in-reply-to :references:date:message-id:user-agent:content-transfer-encoding; bh=vBjAxymPrrnAIU/Gm4whL5UTIeNx/bsZNE59ocnOWmI=; b=g5h0OVgFtsPXr+7zXIeLy0FHPukFMiH/N8NH/ehIEfQDzoNFJzD9ilGTxTeTtdLvoX MWstchgGuXwBWtOuKtaEyGnpLxUA5LL970hKS3cEYVoVq+EsKH2SPMG17VQ+kUhNK7vz J6R32Cv4Pe914K29Nv2ZfbjAOgsz171eqIS3k= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:content-type:subject:from:to:in-reply-to:references:date :message-id:user-agent:content-transfer-encoding; b=eWS4HFTBhv71W1FdGEBMoPY0NfvxXmes72mgmj1BGvglOeXgPwDmzENffZ1hGss4rU SvbCWFJTu0MOdv08Dog1Que56X976w2Bt5uUGZZA3PVXFfJQSPEmhLIRS7XcEulLNO96 ERpvrkW270LyfT37ok5BGIrXI6+i/FgFeTirM= Received: by 10.103.238.5 with SMTP id p5mr916118mur.61.1295471434168; Wed, 19 Jan 2011 13:10:34 -0800 (PST) Received: from localhost (mut38-4-82-233-117-144.fbx.proxad.net [82.233.117.144]) by mx.google.com with ESMTPS id l3sm388847fan.2.2011.01.19.13.10.32 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 19 Jan 2011 13:10:33 -0800 (PST) From: Damien Leone To: sup-devel In-reply-to: <1295467127-sup-6602@medusa> References: <1295445524-sup-9310@ezyang> <1295467127-sup-6602@medusa> Date: Wed, 19 Jan 2011 22:10:20 +0100 Message-Id: <1295471328-sup-9770@mailer> User-Agent: Sup/git Subject: Re: [sup-devel] Strange maildir/OfflineImap/maildir-sync behavior 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 Sup guys, Excerpts from Roni Choudhury's message of mer. janv. 19 21:01:03 +0100 2011: > I've noticed this from time to time as well (along with messages not > disappearing, but instead part of the body appearing, then cut off > with a strange error message about how sup can't load the message). I > find that killing the thread view buffer, then typing @ in index mode > causes these to be fixed. Just mentioning it because it's easier than > restarting sup, and it may be related to the error you describe. I'm > also not sure how to file a bug report of that situation. Yes I have noticed this one, it happens to me mainly when I send a mail then perform a synchronization, probably because the sent mail gets updated from the SentMail maildir (I use gmail), it's on the to-fix list. -- Damien Leone Web: http://dleone.fensalir.fr/ GPG: 0x82EB4DDF _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel