From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.52.162.5 with SMTP id xw5csp8170vdb; Tue, 2 Jul 2013 05:39:22 -0700 (PDT) X-Received: by 10.236.14.37 with SMTP id c25mr14833855yhc.122.1372768761971; Tue, 02 Jul 2013 05:39:21 -0700 (PDT) Return-Path: Received: from rubyforge.org ([50.56.192.79]) by mx.google.com with ESMTP id e68si10226987yha.275.2013.07.02.05.39.21 for ; Tue, 02 Jul 2013 05:39:21 -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 384F52E168; Tue, 2 Jul 2013 12:39:17 +0000 (UTC) X-Greylist: delayed 60363 seconds by postgrey-1.31 at rubyforge; Tue, 02 Jul 2013 12:39:03 UTC Received: from mail-qc0-f175.google.com (mail-qc0-f175.google.com [209.85.216.175]) by rubyforge.org (Postfix) with ESMTP id 731112E14E for ; Tue, 2 Jul 2013 12:39:03 +0000 (UTC) Received: by mail-qc0-f175.google.com with SMTP id k14so3608482qcv.20 for ; Tue, 02 Jul 2013 05:39:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:from:to:subject:in-reply-to:references:date:message-id :user-agent:content-transfer-encoding:x-gm-message-state; bh=k7/FIGPvlPN1qW04VobW5ARcrtT45Eeme9w5Aux8/J8=; b=pTHmWz2K4S6JCIhp0eYTri51uo24SUb8IzL0oUioXpBxJF0olC/81ugPyU8e8/lCDZ 6y0w941KEomuLv2meOwKNFNWYMb8TKZZQCnis+3uVeeEkraUpabMiW/bU3cyN1P3qK18 l/IGIF8zgZ3M/QSrWUV2GP5zmmcvxs2yhqK+3c5gpdee2m8hyJGUeIGGstB5/Bw3OFLm 0A8f3EqRQzn7OwhHp8AZz/a7MqyeS22bMY/QM1qZKhwmgSiFarmxSl073xgTLdLQR/UJ e3lcbh0Qwzk/xwZiqvkHGOXDCvZ/cthwawhQ8qaWsMjPhNZs+qydgJrIsBaAMzaJQ/av CevA== X-Received: by 10.229.118.136 with SMTP id v8mr8951224qcq.18.1372768742096; Tue, 02 Jul 2013 05:39:02 -0700 (PDT) Received: from localhost ([138.110.183.72]) by mx.google.com with ESMTPSA id n7sm36761747qat.1.2013.07.02.05.39.01 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 02 Jul 2013 05:39:01 -0700 (PDT) From: Steven Schmeiser To: sup-talk In-reply-to: <1372717304-sup-142@kpad> References: <72BA4B26-CC25-4DE7-9E05-D93E451F526E@schmeiser.org> <1372717304-sup-142@kpad> Date: Tue, 02 Jul 2013 08:39:00 -0400 Message-Id: <1372768563-sup-3752@indy.local> User-Agent: Sup/git X-Gm-Message-State: ALoCoQkPpqWsU0qYN3Ny99dWgkjsHgwujMOLcAT9ub0cihzl4S8yqBoAiEDKxiXqxPaYYFpt/nv7 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: , 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 I meant your second interpretation: keep the same order, but not have *my* sent messages enter into the date calculation. Maybe it would be possible to create a "latest_received_message" and use that in the sort key. Maybe this will get me to learn a little Ruby... > 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 = 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. > _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk