From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.115.60.6 with SMTP id n6cs54317wak; Sun, 4 Oct 2009 09:43:08 -0700 (PDT) Received: by 10.224.39.71 with SMTP id f7mr2515460qae.373.1254674587150; Sun, 04 Oct 2009 09:43:07 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 8si5323607qyk.124.2009.10.04.09.43.06; Sun, 04 Oct 2009 09:43:07 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-talk-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-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-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 712841D78829; Sun, 4 Oct 2009 12:43:06 -0400 (EDT) X-Greylist: delayed 490 seconds by postgrey-1.31 at rubycentral.org; Sun, 04 Oct 2009 12:32:16 EDT Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.221.179]) by rubyforge.org (Postfix) with ESMTP id D443F16782AF for ; Sun, 4 Oct 2009 12:32:16 -0400 (EDT) Received: by qyk9 with SMTP id 9so4409554qyk.30 for ; Sun, 04 Oct 2009 09:32:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:content-type:cc:subject:from :to:in-reply-to:references:date:message-id:user-agent :content-transfer-encoding; bh=mcOaTAxacJ3XQN7MVBqAaIuZpibHpO11F8NqUindv5U=; b=a8pfFmoiOn6KRGNsPuvH3LkK4x6I3k1A4Okg8nelGTQk35ZEphqlsi+Wbg30ImugKz Wbw/KF/pqn8cMOaWz1yb3aZ3Xz14aMkGUNBMbmezb2rNJZ04hlWx0b9uPon89MzjN8w6 qmkNBSGk92Nhym4t7QSsDkraRfJPcsnRzU4/A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=content-type:cc:subject:from:to:in-reply-to:references:date :message-id:user-agent:content-transfer-encoding; b=XSXSwDYF62xFuGBu6YaFtYtJN/x49YtF4Q1bZMhsUAcebrMMPCIt17Pe1e1e1xxc81 hTYBVJ4A2QAs1PWWB5Fk1JrIdx/GtIz82IMjSgGzNnEqrUEp3ZpynW6WzhSoFv1TO8Dg TgeTgpaplgMfSvIpqMj3YKlPX0LfWHBkaqivw= Received: by 10.224.14.143 with SMTP id g15mr2581077qaa.123.1254673446544; Sun, 04 Oct 2009 09:24:06 -0700 (PDT) Received: from localhost (c-69-141-34-173.hsd1.nj.comcast.net [69.141.34.173]) by mx.google.com with ESMTPS id 7sm2087024qwb.36.2009.10.04.09.24.05 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 04 Oct 2009 09:24:05 -0700 (PDT) From: Bo Borgerson To: William Morgan In-reply-to: <1254415913-sup-6275@masanjin.net> References: <1252789445-30193-1-git-send-email-gigabo@gmail.com> <1254415913-sup-6275@masanjin.net> Date: Sun, 04 Oct 2009 12:23:17 -0400 Message-Id: <1254669536-sup-2700@longword> User-Agent: Sup/git Cc: sup-talk Subject: Re: [sup-talk] [PATCH] Handle added messages in label-list-mode X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup 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-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Excerpts from William Morgan's message of Thu Oct 01 12:53:15 -0400 2009: > Reformatted excerpts from Bo Borgerson's message of 2009-09-12: > > Register label-list-mode with the UpdateManager and handle added > > updates with a reload to keep unread message counts up to date > > Branch label-list-mode-auto-update, merged into next. > Hi William. Thanks for looking at this. > I'm a little concerned with performance, but we'll see how it goes. > Yeah, I think I might be spoiled by my relatively few messages / labels. If it turns out to be an issue maybe it could be made toggle-able with a key-press? (Default off / configurable)? I actually use the label-list-mode as my "home" screen. I like it to stay up-to-date so I can quickly scan which labels have new messages. Incidentally the recent discussion in another thread about making the inbox more like other labels resonates with me. My workflow for all other labels is just to 'x' out when I'm done, but with the inbox I have to '$'ave and 'B'uffer-switch. > What do you think about handling labeled and deleted updates as well? Is there a way to label or delete threads without leaving the label-list-mode? There's already a refresh when switching back to the label-list-mode from elsewhere, I think, so any changes that are $aved should be reflected immediately when you get back. Labels added automatically in a before-add-message hook should already be present when the 'added' update event is received, right? I'm not trying to argue against adding handlers for labeled and deleted updates. I just want to make sure I understand the use cases so I know how to test. Thanks, Bo _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk