From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.96.142.65 with SMTP id ru1csp130901qdb; Sun, 23 Mar 2014 11:55:22 -0700 (PDT) X-Received: by 10.60.172.70 with SMTP id ba6mr52858876oec.17.1395600922503; Sun, 23 Mar 2014 11:55:22 -0700 (PDT) Return-Path: Received: from rubyforge.org ([50.56.192.79]) by mx.google.com with ESMTP id be9si15526849obb.157.2014.03.23.11.55.22 for ; Sun, 23 Mar 2014 11:55:22 -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; dkim=neutral (no key for signature) header.i=@gmail.com; dmarc=fail (p=NONE dis=NONE) header.from=gmail.com Received: from localhost.localdomain (localhost [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 5B39F2E190; Sun, 23 Mar 2014 18:55:23 +0000 (UTC) X-Greylist: delayed 1750 seconds by postgrey-1.31 at rubyforge; Sun, 23 Mar 2014 18:54:28 UTC Received: from mail-we0-f175.google.com (mail-we0-f175.google.com [74.125.82.175]) by rubyforge.org (Postfix) with ESMTP id 41E6A2E188 for ; Sun, 23 Mar 2014 18:54:28 +0000 (UTC) Received: by mail-we0-f175.google.com with SMTP id q58so2825783wes.20 for ; Sun, 23 Mar 2014 11:54:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:in-reply-to:references:date:message-id:user-agent :content-transfer-encoding:mime-version:content-type; bh=GjVY1+EDb9h3tsj2WrjUyd+djdzfx7LKliHuhoKbh+c=; b=dBx+K3eRVOAqNpZ8f90J47Yy+lKkbvhzvQ8nTE23l17iO9ndGjebimtNUHCINAMbi0 6Efvo/LQZ7KAmv/bXxHpLBLsaBIYjJR3UJ0qVw28AY2vM6CoXlHgenJARZL7DqpUen8/ Cn7OFYrZcXCNnucubCurHfwiNwPo0V87aBqRT4VZuAOFwTZ+jePDd85+QE5rsO4aO4E2 AKKD3xQCvkM4Sqgp1Il+wquzq+u0ib+DJ9IqtJqJVwJsMLO9dQPBty9pFWvfFNOgcDXW QBlyML2FqGyN3yiE3PN8Hgihvjup+Dh1msriOcJO7Pt4L2dLoRiMQfWpqSXqxVCYEsOn blkg== X-Received: by 10.180.100.169 with SMTP id ez9mr10750164wib.15.1395599113913; Sun, 23 Mar 2014 11:25:13 -0700 (PDT) Received: from kpad (155-29-190-109.dsl.ovh.fr. [109.190.29.155]) by mx.google.com with ESMTPSA id c7sm27313993wjf.19.2014.03.23.11.25.11 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 23 Mar 2014 11:25:12 -0700 (PDT) Received: from localhost (localhost [IPv6:::1]); by kpad (OpenSMTPD) with ESMTP id 79370132; for ; Sun, 23 Mar 2014 19:25:05 +0100 (CET) From: Matthieu Rakotojaona To: sup-talk In-reply-to: <1395580436-sup-9027@pruts.nl> References: <1395580436-sup-9027@pruts.nl> X-pgp-key: http://otokar.looc2011.eu/static/matthieu.rakotojaona.asc Date: Sun, 23 Mar 2014 19:25:00 +0100 Message-Id: <1395598271-sup-6267@kpad> User-Agent: Sup/git MIME-Version: 1.0 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: , Content-Type: multipart/mixed; boundary="===============5685531807638312632==" Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org --===============5685531807638312632== Content-Transfer-Encoding: 8bit Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=-1395599105-104039-14081-8369-1-=" --=-1395599105-104039-14081-8369-1-= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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. -- = Matthieu Rakotojaona --=-1395599105-104039-14081-8369-1-= Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQJ8BAEBCgBmBQJTLycBXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQwNkQ3NDcxMDJFRUU4MEYwRTY4MzQwMkEz QTc0RTE5NDVDM0Q5NzIyAAoJEDp04ZRcPZciZKAP/2oeJjv94xONlLEnyYq/R/oL 72mxwTXe93wqTN6nnu8Ia5gGfPndtLAsK+LjWmvKVVyk0AVhs1VXKWe7YfQ4ixwO fy/cUXy8G2coVMCjylb326xQ+TKAW/Z4XDKj2fyNOOZ8mvI9V77RRmxNWcBWLTSU w+D4nu0/goXFxpRzebQhoqy3EM+YDCS9Fa0PsmJ4eks3CZyL79YQRBr/IEuPIQNT pCt3Ql3l7bigb9aJ4x6Dk5tDAhu0RNRImFSguP5GdwUE32CMuglk6j7B7NxR0FHc S3xLnMWyLYQK+nYFKfDUTmq/ej4+TS1m7AjADZwHhIsIkaHuqABHOjoWU6q7489e pMcfmjlbZFjYQKd/4ZuEQIehZKG+72LfgJ/JF3Xxh4TkESjkDJoUnBVnnpLLrc2p t/rnN3IIL9GHXFzHgDiIJmcyHgZGv1vD4pe9wp5WHzJArfa6Vo0qt1VmyTcCAiiQ wBTodaDpy9LX2daQ1t1hnW1kEymuS81kZN2Sg32k9d0dAofhrYcwtOa806yYwWVF 7JFZk0YaUlHiTQSBT3Qsh0oPZbVJqzmgeur71SIMD4A4f+Utl/TLuPzt8WbgnIqx YjhtB8awYe3fJJuoeT0aM0OZjbMfyWZXWG/X+ciKCIaAOOJB7iRykQFmilSpHZgG IK9O+GYHkLxiMA/oNrGB =PJCG -----END PGP SIGNATURE----- --=-1395599105-104039-14081-8369-1-=-- --===============5685531807638312632== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk --===============5685531807638312632==--