From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.42.172.201 with SMTP id o9cs86026icz; Sun, 14 Nov 2010 18:11:37 -0800 (PST) Received: by 10.42.178.65 with SMTP id bl1mr110378icb.140.1289787095913; Sun, 14 Nov 2010 18:11:35 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id s9si18047202ibe.3.2010.11.14.18.11.35; Sun, 14 Nov 2010 18:11:35 -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 8E6F6177994D; Sun, 14 Nov 2010 21:11:35 -0500 (EST) X-Greylist: delayed 300 seconds by postgrey-1.31 at rubyforge.org; Sun, 14 Nov 2010 20:47:45 EST Received: from dmz-mailsec-scanner-5.mit.edu (DMZ-MAILSEC-SCANNER-5.MIT.EDU [18.7.68.34]) by rubyforge.org (Postfix) with ESMTP id D6347185838D for ; Sun, 14 Nov 2010 20:47:45 -0500 (EST) X-AuditID: 12074422-b7c3eae000000a70-9d-4ce0901560ef Received: from mailhub-auth-3.mit.edu ( [18.9.21.43]) by dmz-mailsec-scanner-5.mit.edu (Symantec Brightmail Gateway) with SMTP id 9C.AF.02672.51090EC4; Sun, 14 Nov 2010 20:42:45 -0500 (EST) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id oAF1gi5K015752; Sun, 14 Nov 2010 20:42:44 -0500 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 oAF1ggII001944; Sun, 14 Nov 2010 20:42:43 -0500 (EST) From: "Edward Z. Yang" To: Matthias Vallentin In-reply-to: <20101115004931.GD34938@icsi.berkeley.edu> References: <20101115004931.GD34938@icsi.berkeley.edu> Date: Sun, 14 Nov 2010 20:42:42 -0500 Message-Id: <1289785328-sup-6895@ezyang> User-Agent: Sup/git X-Brightmail-Tracker: AAAAAQCq+Kk= Cc: sup-talk Subject: Re: [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: , 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 Matthias Vallentin's message of Sun Nov 14 19:49:31 -0500 2010: > 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? I use the keybinding 'U', which performs the is:unread search. Cheers, Edward _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk