community/pipermail-archives/sup-talk/2013-07.txt (4628B) - raw
1 From steven@schmeiser.org Mon Jul 1 19:47:36 2013
2 From: steven@schmeiser.org (Steven Schmeiser)
3 Date: Mon, 1 Jul 2013 15:47:36 -0400
4 Subject: [sup-talk] ignore replies when calculating thread date
5 Message-ID: <72BA4B26-CC25-4DE7-9E05-D93E451F526E@schmeiser.org>
6
7 Hi all,
8 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.
9
10 Cheers,
11 Steve
12
13
14 From matthieu.rakotojaona@gmail.com Mon Jul 1 22:26:48 2013
15 From: matthieu.rakotojaona@gmail.com (Matthieu Rakotojaona)
16 Date: Tue, 02 Jul 2013 00:26:48 +0200
17 Subject: [sup-talk] ignore replies when calculating thread date
18 In-Reply-To: <72BA4B26-CC25-4DE7-9E05-D93E451F526E@schmeiser.org>
19 References: <72BA4B26-CC25-4DE7-9E05-D93E451F526E@schmeiser.org>
20 Message-ID: <1372717304-sup-142@kpad>
21
22 Excerpts from Steven Schmeiser's message of 2013-07-01 21:47:36 +0200:
23 > Is there an option to ignore replies when calculating the date of a
24 > thread? I would like it if replying to a thread did not bump it to
25 > the top of the index.
26
27 Basically, you would like to change the sorting order from
28 date-of-last-message to date-of-first-message ?
29
30 There is nothing currently implemented for this, at least that I know
31 of. If you're aventurous enough, you can have some option modify the
32 ThreadSet#sort_key method. Here's the current content:
33
34 ```
35 def sort_key
36 m = latest_message
37 m ? [-m.date.to_i, m.id] : [-Time.now.to_i, ""]
38 end
39 ```
40
41 Pretty straightforward, you'd have to fetch first_message and keep the
42 same logic.
43
44 However, if you only want to keep the same order independently from
45 _your_ replies, I don't know how you would do it.
46
47 --
48 Matthieu Rakotojaona
49 -------------- next part --------------
50 A non-text attachment was scrubbed...
51 Name: signature.asc
52 Type: application/pgp-signature
53 Size: 836 bytes
54 Desc: not available
55 URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20130702/5b28c674/attachment.bin>
56
57 From steven@schmeiser.org Tue Jul 2 12:39:00 2013
58 From: steven@schmeiser.org (Steven Schmeiser)
59 Date: Tue, 02 Jul 2013 08:39:00 -0400
60 Subject: [sup-talk] ignore replies when calculating thread date
61 In-Reply-To: <1372717304-sup-142@kpad>
62 References: <72BA4B26-CC25-4DE7-9E05-D93E451F526E@schmeiser.org>
63 <1372717304-sup-142@kpad>
64 Message-ID: <1372768563-sup-3752@indy.local>
65
66 I meant your second interpretation: keep the same order, but not have
67 *my* sent messages enter into the date calculation. Maybe it would be
68 possible to create a "latest_received_message" and use that in the sort
69 key.
70
71 Maybe this will get me to learn a little Ruby...
72
73 > Excerpts from Steven Schmeiser's message of 2013-07-01 21:47:36 +0200:
74 > > Is there an option to ignore replies when calculating the date of a
75 > > thread? I would like it if replying to a thread did not bump it to
76 > > the top of the index.
77 >
78 > Basically, you would like to change the sorting order from
79 > date-of-last-message to date-of-first-message ?
80 >
81 > There is nothing currently implemented for this, at least that I know
82 > of. If you're aventurous enough, you can have some option modify the
83 > ThreadSet#sort_key method. Here's the current content:
84 >
85 > ```
86 > def sort_key
87 > m = latest_message
88 > m ? [-m.date.to_i, m.id] : [-Time.now.to_i, ""]
89 > end
90 > ```
91 >
92 > Pretty straightforward, you'd have to fetch first_message and keep the
93 > same logic.
94 >
95 > However, if you only want to keep the same order independently from
96 > _your_ replies, I don't know how you would do it.
97 >
98
99 From steven@schmeiser.org Wed Jul 10 02:44:59 2013
100 From: steven@schmeiser.org (Steven Schmeiser)
101 Date: Wed, 10 Jul 2013 02:44:59 -0000
102 Subject: [sup-talk] always use async editing?
103 Message-ID: <1373410624-sup-1657@indy.local>
104
105
106 Is there a way to always use async editing when composing a reply or new
107 message? Right now, when I reply to a message, I hit 'E' then 'H' to
108 launch my async editor. Can this be configured as the default
109 behavior and can asyn mode be used to compose new messages (without
110 going back and editing a draft?)
111
112 Steve
113
114 From steven@schmeiser.org Mon Jul 15 19:09:58 2013
115 From: steven@schmeiser.org (Steven Schmeiser)
116 Date: Mon, 15 Jul 2013 19:09:58 -0000
117 Subject: [sup-talk] always use async mode
118 Message-ID: <1373915207-sup-8940@indy.local>
119
120 Hi all,
121 Is there a way to always launch the async editor when replying to or
122 composing a new message? For replies, I always hit 'E' then 'H' and it
123 would be nice for this to be a configurable default. And I haven't
124 found a way to async edit a new message other than close the default
125 editor, then open the message back up with 'E' and 'H'.
126
127 Thanks,
128 Steve
129