From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.52.162.5 with SMTP id xw5csp161697vdb; Mon, 1 Jul 2013 16:36:00 -0700 (PDT) X-Received: by 10.236.123.210 with SMTP id v58mr13811376yhh.64.1372721760204; Mon, 01 Jul 2013 16:36:00 -0700 (PDT) Return-Path: Received: from rubyforge.org ([50.56.192.79]) by mx.google.com with ESMTP id 48si10467283yhi.199.2013.07.01.16.36.00 for ; Mon, 01 Jul 2013 16:36:00 -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 (bad format) header.i=@gmail.com Received: from localhost.localdomain (localhost [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 550DE2E15D; Mon, 1 Jul 2013 23:36:01 +0000 (UTC) X-Greylist: delayed 2076 seconds by postgrey-1.31 at rubyforge; Mon, 01 Jul 2013 23:35:44 UTC Received: from mail-wg0-f46.google.com (mail-wg0-f46.google.com [74.125.82.46]) by rubyforge.org (Postfix) with ESMTP id 2EE712E145 for ; Mon, 1 Jul 2013 23:35:44 +0000 (UTC) Received: by mail-wg0-f46.google.com with SMTP id c11so4201565wgh.25 for ; Mon, 01 Jul 2013 16:35:42 -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:x-pgp-key:date:message-id :user-agent:content-transfer-encoding:mime-version:content-type; bh=WiXV7WARE3+Om0hQSjpAHvbfTqVzuKmMhn+wCDOEuBg=; b=xwbpni6lzeWkqXwU2A3H3UavedfGbf5d1Cf0KZWeIZ7hxPW0ifFsrEJo7KuPZcjEiw FkvwVdSu7V8GNoiZO7Rf6HrHs/WFOnjJQiXabSod4xUC+PD6dc6r42chHFXL51nfHAZX 9RzrAACtMI/skAY6YXVq79422uR556FO871qhhMs/nS+NqBrruznNmpADRBf1HLcv0Op 6HHljo4HUqLKoLFwp0TsVMzUx7LFcWKIjQIU62zERNvsYvOauGyBIqRBuq11c8PTMQf9 qqq71a9sozfBEoT0H5PTuv97tdqyH7szFNMbyDB5iDcqht767BtYxL6XvHq26TkgO/4f 9ybA== X-Received: by 10.194.108.73 with SMTP id hi9mr21385199wjb.85.1372718217499; Mon, 01 Jul 2013 15:36:57 -0700 (PDT) Received: from kpad (155-29-190-109.dsl.ovh.fr. [109.190.29.155]) by mx.google.com with ESMTPSA id u9sm19278943wif.6.2013.07.01.15.36.55 for (version=TLSv1.2 cipher=AES128-SHA bits=128/128); Mon, 01 Jul 2013 15:36:56 -0700 (PDT) Received: from localhost (1000@localhost [local]); by kpad (OpenSMTPD) with ESMTP id 2e75f458; for ; Mon, 1 Jul 2013 22:26:54 +0000 (UTC) From: Matthieu Rakotojaona To: sup-talk In-reply-to: <72BA4B26-CC25-4DE7-9E05-D93E451F526E@schmeiser.org> References: <72BA4B26-CC25-4DE7-9E05-D93E451F526E@schmeiser.org> X-pgp-key: http://otokar.looc2011.eu/static/matthieu.rakotojaona.asc Date: Tue, 02 Jul 2013 00:26:48 +0200 Message-Id: <1372717304-sup-142@kpad> User-Agent: Sup/git MIME-Version: 1.0 Subject: Re: [sup-talk] ignore replies when calculating thread date 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="===============6905435662521363762==" Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org --===============6905435662521363762== Content-Transfer-Encoding: 8bit Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=-1372717614-232091-26943-268-1-=" --=-1372717614-232091-26943-268-1-= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Excerpts from Steven Schmeiser's message of 2013-07-01 21:47:36 +0200: > Is there an option to ignore replies when calculating the date of a > thread? I would like it if replying to a thread did not bump it to > the top of the index. Basically, you would like to change the sorting order from date-of-last-message to date-of-first-message ? There is nothing currently implemented for this, at least that I know of. If you're aventurous enough, you can have some option modify the ThreadSet#sort_key method. Here's the current content: ``` def sort_key m =3D latest_message m ? [-m.date.to_i, m.id] : [-Time.now.to_i, ""] end ``` Pretty straightforward, you'd have to fetch first_message and keep the same logic. However, if you only want to keep the same order independently from _your_ replies, I don't know how you would do it. -- = Matthieu Rakotojaona --=-1372717614-232091-26943-268-1-= Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (GNU/Linux) iQIcBAEBAgAGBQJR0gIuAAoJEDp04ZRcPZci5F0P/itx1LXc7ETnFadBQLchnNTm BJj3OtnPVOj02pyyrqK0SEj0wynxS/uS/AqR8UoEiBoZQtoHhCUuJT2CfAmRPCYk eAx6ns1GiMbkOd/cChS0SHSoP1jadlCltz/l3geZgewF1dgHftyBErNkrULOVl1C lXBpMBgdEcHbckNwOO6J+/6sqTlL8x4z0rUQOCggVfDXBV2QEoBi09CSNznBwItO M7/V3YtbZkMFUZnrddWLkT8uLGmGIKnC+g1v2rfF4uMsSSiPMauJG6E8I+FE1rNP M8XcZiwsb9R0c7xeSYXd35eLqJFySOCQtFU4JvpNGEHHExN4FfSTmSQMNriifSgP cRlug1MPwtT3SOGsdFdJHmNdWw3N9ZZLO95sJVC7YNgJHP7xDy8kxlwtfIy5qrGm AYVMzWAEpRgrQPmqxxREkDggufrnrS1h7OPs2kETYwHcX7ReZycdPK1FKnMmQDsC EHaNrinXVJnSN1az0PXMIQUWAfF51IW0EsJnOFQftSihMd81pBwhgZwgRGKSFX0U fb6FQ2xHDKmLc+j0OHmmKEHU+1GBa71Uk8MB7YA/rURMWzcquntzt+iSEMury6HG DawMxGbkbgLAGd4Z6akDTRcF23Z//W7emCnpmcQivhAGEA4953iIcEeeKL/KY+tc 2TXGoJSkMvv3Dod05fCX =gHZC -----END PGP SIGNATURE----- --=-1372717614-232091-26943-268-1-=-- --===============6905435662521363762== 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 --===============6905435662521363762==--