From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.142.178.13 with SMTP id a13cs47087wff; Mon, 23 May 2011 01:43:31 -0700 (PDT) Received: by 10.229.95.144 with SMTP id d16mr1510569qcn.37.1306140211050; Mon, 23 May 2011 01:43:31 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id e20si11430393qck.147.2011.05.23.01.43.29; Mon, 23 May 2011 01:43:30 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-devel-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-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id C4576185836C for ; Mon, 23 May 2011 04:43:28 -0400 (EDT) X-Greylist: delayed 333 seconds by postgrey-1.31 at rubyforge.org; Mon, 23 May 2011 04:03:26 EDT Received: from ping.pong.ch (ping.pong.ch [77.109.141.101]) by rubyforge.org (Postfix) with ESMTP id 7D2E9185836C for ; Mon, 23 May 2011 04:03:26 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by ping.pong.ch (Postfix) with ESMTP id D0C1D40E2539 for ; Mon, 23 May 2011 09:57:46 +0200 (CEST) Received: from ping.pong.ch ([127.0.0.1]) by localhost (ping.pong.ch [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bLnJN2jc7Jkb for ; Mon, 23 May 2011 09:57:46 +0200 (CEST) Received: from auth sender gaudenz@ping.pong.ch by ping.pong.ch (Postfix) with ESMTPSA id D4A5D40C25C3 for ; Mon, 23 May 2011 09:57:44 +0200 (CEST) Received: by meteor.durcheinandertal.local (Postfix, from userid 1000) id BC5E56258B; Mon, 23 May 2011 09:52:43 +0200 (CEST) From: Gaudenz Steinlin To: sup-devel In-reply-to: <1306101722-sup-3610@masanjin.net> References: <1305471101-sup-6655@masanjin.net> <1305693289-sup-4896@masanjin.net> <1305748878-sup-7940@xo15-sascha.sascha.silbe.org> <1306101722-sup-3610@masanjin.net> Date: Mon, 23 May 2011 09:52:43 +0200 Message-Id: <1306136821-sup-9611@meteor.durcheinandertal.local> User-Agent: Sup/git Subject: Re: [sup-devel] Query for largest msg_id? X-BeenThere: sup-devel@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Sup developer discussion List-Id: Sup developer discussion 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-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org Excerpts from William Morgan's message of 2011-05-23 00:05:57 +0200: > Reformatted excerpts from Sascha Silbe's message of 2011-05-18: > > If heliotrope permanently erases the copies (instead of just not > > exposing UI to access them), that would be a major step backwards. > > What do you suggest as a way of exposing duplicates within the UI? I > worry that just keeping all copies of a message around will make the > thread structure messy. Is there a better alternative? Merging the messages is fine and actually an improvement over other MUAs. But adding a line in the header section indicating the source and how often the message appears in the source would be nice. Like Sources: maildir://bla/blu (2), maildir://foo/bar (1) Also if you display the message in the raw form (V key in sup), then all the copies could be shown in full. This would help diagnosing why you receive duplicates of certain messages. Gaudenz -- Ever tried. Ever failed. No matter. Try again. Fail again. Fail better. ~ Samuel Beckett ~ _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel