Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Steven Schmeiser <steven@schmeiser.org>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] ignore replies when calculating thread date
Date: Tue, 02 Jul 2013 08:39:00 -0400	[thread overview]
Message-ID: <1372768563-sup-3752@indy.local> (raw)
In-Reply-To: <1372717304-sup-142@kpad>

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


      reply	other threads:[~2013-07-02 12:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-01 19:47 Steven Schmeiser
2013-07-01 22:26 ` Matthieu Rakotojaona
2013-07-02 12:39   ` Steven Schmeiser [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1372768563-sup-3752@indy.local \
    --to=steven@schmeiser.org \
    --cc=sup-talk@rubyforge.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox