From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.96.142.65 with SMTP id ru1csp133130qdb; Sun, 23 Mar 2014 12:58:41 -0700 (PDT) X-Received: by 10.182.113.195 with SMTP id ja3mr2998254obb.46.1395604721024; Sun, 23 Mar 2014 12:58:41 -0700 (PDT) Return-Path: Received: from rubyforge.org ([50.56.192.79]) by mx.google.com with ESMTP id ov10si15678958obc.140.2014.03.23.12.58.40 for ; Sun, 23 Mar 2014 12:58:41 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 50.56.192.79 as permitted sender) client-ip=50.56.192.79; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 50.56.192.79 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from localhost.localdomain (localhost [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id C898A2E1CF; Sun, 23 Mar 2014 19:58:41 +0000 (UTC) Received: from fe2.pruts.nl (pruts.nl [82.94.235.106]) by rubyforge.org (Postfix) with ESMTP id 8C1302E188 for ; Sun, 23 Mar 2014 19:57:38 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by fe2.pruts.nl (Postfix) with ESMTP id E1A6914005F for ; Sun, 23 Mar 2014 20:57:34 +0100 (CET) X-Virus-Scanned: amavisd-new at pruts.nl Received: from fe2.pruts.nl ([IPv6:::ffff:127.0.0.1]) by localhost (fe2.local [::ffff:127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5dTIiKm7b1Ql for ; Sun, 23 Mar 2014 20:57:31 +0100 (CET) Received: by fe2.pruts.nl (Postfix, from userid 1000) id BA3FF140095; Sun, 23 Mar 2014 20:57:31 +0100 (CET) From: Ico Doornekamp To: sup-talk In-reply-to: <1395598271-sup-6267@kpad> References: <1395580436-sup-9027@pruts.nl> <1395598271-sup-6267@kpad> X-pgp-key: 4202FA2F X-pgp-keyserver: subkeys.pgp.net X-pgp-fingerprint: F042 F5CD B0A6 EC6A CB80 A829 CACD A4B5 4202 FA2F Date: Sun, 23 Mar 2014 20:57:31 +0100 Message-Id: <1395604436-sup-3844@pruts.nl> User-Agent: Sup/0.15.3 Subject: Re: [sup-talk] Recognizing new mails. 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 Sorry for the noise, I caused this problem myself: I use some mail filtering using procmail to set the 'X-Mark-As-Read: yes' flag for bulk mail (mailing lists etc) so these do not trigger my you-have-new-mail bells and whistles. I was kind of confused about the difference between 'new' and 'unread' mail, thus messing up sup's behaviour. * On 2014-03-23 19:25:00 +0100, Matthieu Rakotojaona wrote: > Excerpts from Ico's message of 2014-03-23 14:15:51 +0100: > > Does sup track read/unread for individual mails? For example, I open a > > thread with 3 mails and read them all. The thread drops from my inbox. > > > > A few hours later I find the thread back in my inbox and open it again, > > it now has 6 mails. How do I know which 3 are the new ones? Only the > > last one is opened by default, but how do I tell which others I still > > need to read? > > > > Is there a way to have unread mails unfolded by default? > > Weird, on my sup I have all new mails unfolded by default, and the focus > is on the first one that is unfolded (either because it's unread or > starred). That state is kept separately for each message indeed, so in > your scenario it behaves as you expect. What version are you running ? > > You can see which message is unread with the 'N' on each message's top > line. > -- :wq ^X^Cy^K^X^C^C^C^C _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk