From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.42.172.201 with SMTP id o9cs85668icz; Sun, 14 Nov 2010 17:34:04 -0800 (PST) Received: by 10.42.221.136 with SMTP id ic8mr2482084icb.298.1289784843732; Sun, 14 Nov 2010 17:34:03 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id ga18si17931722ibb.68.2010.11.14.17.34.03; Sun, 14 Nov 2010 17:34:03 -0800 (PST) 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 Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 650CB1858396; Sun, 14 Nov 2010 20:34:03 -0500 (EST) X-Greylist: delayed 378 seconds by postgrey-1.31 at rubyforge.org; Sun, 14 Nov 2010 19:55:55 EST Received: from gateway0.EECS.Berkeley.EDU (gateway0.EECS.Berkeley.EDU [169.229.60.87]) by rubyforge.org (Postfix) with ESMTP id 84117185838C for ; Sun, 14 Nov 2010 19:55:55 -0500 (EST) Received: from icsi.berkeley.edu (wangari.CS.Berkeley.EDU [169.229.3.78]) (authenticated bits=0) by gateway0.EECS.Berkeley.EDU (8.14.4/8.13.5) with ESMTP id oAF0nVYY019935 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Sun, 14 Nov 2010 16:49:33 -0800 (PST) Date: Sun, 14 Nov 2010 16:49:31 -0800 From: Matthias Vallentin To: sup-talk Message-ID: <20101115004931.GD34938@icsi.berkeley.edu> Mail-Followup-To: sup-talk MIME-Version: 1.0 Content-Disposition: inline X-PGP-Fingerprint: 8A3B 1323 B469 CCBA 54D3 3BCC D5E7 8DF5 9C8D 4B41 User-Agent: Mutt/1.5.20 (2009-06-14) Subject: [sup-talk] (no subject) 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: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org I am a Mutt user interested in switching to Sup. One thing that is not clear to me is how to find new unread messages that skipped the inbox. Coming from the world of mail folders, I can monitor each folder for unread messages and switch to it when I see that a new one has arrived. Often, a buffy tool (or the Mutt sidebar) can be used to display the various folders with their new message counts. How would that mindset translate to Sup? Would I have to regularly query all (or a just a subset of) labels to get an idea whether label X "received" a new message? Matthias _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk