community/pipermail-archives/sup-devel/2010-12.txt (29614B) - raw
1 From gaudenz@soziologie.ch Wed Dec 1 03:37:58 2010
2 From: gaudenz@soziologie.ch (Gaudenz Steinlin)
3 Date: Wed, 01 Dec 2010 09:37:58 +0100
4 Subject: [sup-devel] [PATCH] Converted crypto to use the gpgme gem
5 In-Reply-To: <1291097850-sup-6043@tilus.net>
6 References: <AANLkTinrSAheJb2F4Xw9AmgXcGLxeQh0_MEnuTSATye_@mail.gmail.com>
7 <AANLkTinXwKiJqgKyFrrcVV21a8j8hV=fw4QcvDLhtM8E@mail.gmail.com>
8 <AANLkTi=7yasVvAW4P85v3GJxf+quJrE3-1XruDgUZq+D@mail.gmail.com>
9 <1289466286-sup-7540@meteor.durcheinandertal.local>
10 <AANLkTikUwyX6xj-f_ZnLp6s2s9vaCpgayPKygniWndoJ@mail.gmail.com>
11 <1289907535-sup-3989@meteor.durcheinandertal.local>
12 <AANLkTi=xz16ecZ0C5=RUcOG4wzojVVzs70PZ2ueKa0ht@mail.gmail.com>
13 <1289932061-sup-96@meteor.durcheinandertal.local>
14 <AANLkTin=1MRrW0vuj_7uMvjcyLc3Aaw4ddZ_Rq6TBiyx@mail.gmail.com>
15 <AANLkTinvv59bWu0UfjW2K-xDRUP42tDwmgMh5yZdmaN_@mail.gmail.com>
16 <1291023322-sup-8457@meteor.durcheinandertal.local>
17 <1291097850-sup-6043@tilus.net>
18 Message-ID: <1291192005-sup-7698@meteor.durcheinandertal.local>
19
20 Excerpts from Tero Tilus's message of Die Nov 30 07:22:48 +0100 2010:
21 > Gaudenz Steinlin, 2010-11-29 11:41:
22 > > As far as I understood the branch layout the flow of changes is
23 > > master -> next -> release. So applying to next would mean it ends up
24 > > in the next release (0.12).
25 >
26 > Master is considered "stable" and next "unstable". Releases are
27 > tagged from master and small changes may go directly to master. New
28 > features are introduced in next and merged to master when they are
29 > considered stable (enough).
30
31 Thanks for clarifying this.At the moment this does not seem to reflect
32 the current reality in the git repository. Master has quite a lot of
33 commits next does not have. Also next has not been updated since
34 several months.
35
36 I guess this is due to the fact that there were no major code changes
37 during the last months and therefore all the work has been done
38 directly on master.
39
40 Gaudenz
41 --
42 Ever tried. Ever failed. No matter.
43 Try again. Fail again. Fail better.
44 ~ Samuel Beckett ~
45
46 From sup-bugs@masanjin.net Wed Dec 1 09:42:34 2010
47 From: sup-bugs@masanjin.net (plutek)
48 Date: Wed, 01 Dec 2010 14:42:34 +0000
49 Subject: [sup-devel] [issue135] crash on attempting to start sup
50 In-Reply-To: <1291214554.07.0.588958545349.issue135@masanjin.net>
51 Message-ID: <1291214554.07.0.588958545349.issue135@masanjin.net>
52
53
54 New submission from plutek <plutek at infinity.net>:
55
56 this morning, after running sup-sync -a, sup will not start -- it crashes
57 immediately. i've been running this version of sup successfully for a long time
58 now, and haven't changed my usage pattern at all.
59
60 attached is my .sup/exception-log.txt
61
62 cheers!
63
64 ----------
65 files: exception-log.txt
66 messages: 317
67 nosy: plutek
68 priority: bug
69 ruby_version: 1.8
70 status: unread
71 sup_version: 0.11
72 title: crash on attempting to start sup
73
74 _________________________________________
75 Sup issue tracker <sup-bugs at masanjin.net>
76 <http://masanjin.net/sup-bugs/issue135>
77 _________________________________________
78 -------------- next part --------------
79 --- RuntimeError from thread: load threads for thread-index-mode
80 wrong id called on nil
81 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup.rb:17:in `id'
82 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/modes/thread-index-mode.rb:234:in `update'
83 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/hook.rb:123:in `sort_by'
84 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/modes/thread-index-mode.rb:234:in `each'
85 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/modes/thread-index-mode.rb:234:in `sort_by'
86 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/modes/thread-index-mode.rb:234:in `update'
87 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/modes/thread-index-mode.rb:232:in `synchronize'
88 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/modes/thread-index-mode.rb:232:in `update'
89 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/modes/thread-index-mode.rb:643:in `__unprotected_load_n_threads'
90 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/thread.rb:334:in `load_n_threads'
91 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/index.rb:148:in `each_id_by_date'
92 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/index.rb:239:in `each_id'
93 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/index.rb:239:in `each'
94 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/index.rb:239:in `each_id'
95 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/index.rb:148:in `each_id_by_date'
96 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/thread.rb:328:in `load_n_threads'
97 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/modes/thread-index-mode.rb:640:in `__unprotected_load_n_threads'
98 (eval):12:in `load_n_threads'
99 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/modes/thread-index-mode.rb:624:in `load_n_threads_background'
100 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup.rb:76:in `reporting_thread'
101 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup.rb:74:in `initialize'
102 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup.rb:74:in `new'
103 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup.rb:74:in `reporting_thread'
104 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/modes/thread-index-mode.rb:623:in `load_n_threads_background'
105 /usr/lib/ruby/gems/1.8/gems/sup-0.11/lib/sup/modes/thread-index-mode.rb:694:in `__unprotected_load_threads'
106 (eval):12:in `load_threads'
107 /usr/lib/ruby/gems/1.8/gems/sup-0.11/bin/sup:231
108 /usr/bin/sup:19:in `load'
109 /usr/bin/sup:19
110
111 From dmishd@gmail.com Mon Dec 6 18:31:43 2010
112 From: dmishd@gmail.com (Hamish D)
113 Date: Mon, 6 Dec 2010 23:31:43 +0000
114 Subject: [sup-devel] [PATCH] Converted crypto to use the gpgme gem
115 In-Reply-To: <1291023322-sup-8457@meteor.durcheinandertal.local>
116 References: <AANLkTinrSAheJb2F4Xw9AmgXcGLxeQh0_MEnuTSATye_@mail.gmail.com>
117 <AANLkTinXwKiJqgKyFrrcVV21a8j8hV=fw4QcvDLhtM8E@mail.gmail.com>
118 <AANLkTi=7yasVvAW4P85v3GJxf+quJrE3-1XruDgUZq+D@mail.gmail.com>
119 <1289466286-sup-7540@meteor.durcheinandertal.local>
120 <AANLkTikUwyX6xj-f_ZnLp6s2s9vaCpgayPKygniWndoJ@mail.gmail.com>
121 <1289907535-sup-3989@meteor.durcheinandertal.local>
122 <AANLkTi=xz16ecZ0C5=RUcOG4wzojVVzs70PZ2ueKa0ht@mail.gmail.com>
123 <1289932061-sup-96@meteor.durcheinandertal.local>
124 <AANLkTin=1MRrW0vuj_7uMvjcyLc3Aaw4ddZ_Rq6TBiyx@mail.gmail.com>
125 <AANLkTinvv59bWu0UfjW2K-xDRUP42tDwmgMh5yZdmaN_@mail.gmail.com>
126 <1291023322-sup-8457@meteor.durcheinandertal.local>
127 Message-ID: <AANLkTi=AJZGLAra20fQvEvU0EasQ_1yWpsr6+4TV3iEn@mail.gmail.com>
128
129 > I just discovered another problem: If the secret key is not available
130 > (because it's on a removable media and the media is not mounted), the
131 > mail is sent anyway. While this is just a bit annoying for signed mail
132 > it definitely should not happen for encrypted mails. Current sup
133 > corectly fails in this case.
134
135 I have replicated this (by turning off gpg agent) but I'm confused as
136 to why this is happening. If I try the same steps in irb I get an
137 exception, and this should be caught and dealt with in the same way as
138 current sup does. I guess I'll have to keep trying to replicate more
139 and more of the path way through ... sigh.
140
141 Once I have worked out the proper logic I can then add some extra
142 checks for ensuring that gpg agent is running and that sup knows where
143 to find it. I could even have sup ask you for your gpg passphrase with
144 gpgme. There might be some security issues with having ruby ask you
145 for your passphrase I guess, but I don't think it would be worse than
146 gpg agent. gpg agent doesn't seem to have the suid bit set, though
147 maybe as a C program it can be more rigorous about overwriting your
148 passphrase in memory. I could always implement it as a hook with gpg
149 agent as the default.
150
151 > It would also be nice to have different colors for different trust
152 > levels. So you don't have to expand the extra information to see if a
153 > valid signature is trusted or not. Is this already possible with the
154 > current hook?
155
156 That requires code changes, but I've done that and attached a patch
157 (intended to go on top of the other 4 patches). Now untrusted
158 signatures have a blue background. (Trusted signatures have a default
159 background - black normally, and bad signatures have a red
160 background). All signatures have yellow text.
161
162 I'm quite open to a different colour scheme being chosen if someone
163 thinks something else would be clearer.
164
165 Hamish Downer
166 -------------- next part --------------
167 A non-text attachment was scrubbed...
168 Name: 0005-added-color-for-untrusted-cryptonotice.patch
169 Type: text/x-patch
170 Size: 4170 bytes
171 Desc: not available
172 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20101206/35adb245/attachment-0001.bin>
173
174 From sup-bugs@masanjin.net Wed Dec 8 13:59:56 2010
175 From: sup-bugs@masanjin.net (anonymous)
176 Date: Wed, 08 Dec 2010 18:59:56 +0000
177 Subject: [sup-devel] [issue136] Crash when searching for during:december
178 In-Reply-To: <1291834796.86.0.985380843914.issue136@masanjin.net>
179 Message-ID: <1291834796.86.0.985380843914.issue136@masanjin.net>
180
181
182 New submission from anonymous:
183
184 When searching for "during:december", I get the following exception. Searching
185 for e.g. "during:june" works fine.
186
187 /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/index.rb:800:in `index_text'
188 /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/index.rb:681:in
189 `index_message_static'
190 /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/index.rb:642:in `sync_message'
191 /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/util.rb:609:in `send'
192 /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/util.rb:609:in `method_missing'
193 /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/poll.rb:188:in `poll_from'
194 /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/maildir.rb:144:in `poll'
195 /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/maildir.rb:143:in `each'
196 /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/maildir.rb:143:in `poll'
197 /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/poll.rb:174:in `poll_from'
198 /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/util.rb:609:in `send'
199 /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/util.rb:609:in `method_missing'
200 /usr/lib/ruby/gems/1.8/gems/sup-999/bin/sup-sync:123
201 /usr/lib/ruby/gems/1.8/gems/sup-999/bin/sup-sync:118:in `each'
202 /usr/lib/ruby/gems/1.8/gems/sup-999/bin/sup-sync:118
203 /usr/bin/sup-sync:19:in `load'
204 /usr/bin/sup-sync:19
205
206 ----------
207 messages: 319
208 nosy: anonymous
209 priority: bug
210 ruby_version: 1.8.7 (2010-01-10 patchlevel 249) [x86_64-linux]
211 status: unread
212 sup_version: 9f86033
213 title: Crash when searching for during:december
214
215 _________________________________________
216 Sup issue tracker <sup-bugs at masanjin.net>
217 <http://masanjin.net/sup-bugs/issue136>
218 _________________________________________
219
220 From sup-bugs@masanjin.net Thu Dec 9 23:27:33 2010
221 From: sup-bugs@masanjin.net (anonymous)
222 Date: Fri, 10 Dec 2010 04:27:33 +0000
223 Subject: [sup-devel] [issue137] "wrong id called on nil" when searching
224 In-Reply-To: <1291955252.92.0.499188876837.issue137@masanjin.net>
225 Message-ID: <1291955252.92.0.499188876837.issue137@masanjin.net>
226
227
228 New submission from anonymous:
229
230 When I search for messages from a specific person, sup crashes with this error.
231 Searching for anyone or anything else works.
232
233 ----------
234 keyword: maildir
235 messages: 320
236 nosy: anonymous
237 priority: feature request
238 ruby_version: 1.8
239 status: unread
240 sup_version: 0.11
241 title: "wrong id called on nil" when searching
242
243 _________________________________________
244 Sup issue tracker <sup-bugs at masanjin.net>
245 <http://masanjin.net/sup-bugs/issue137>
246 _________________________________________
247
248 From sup-bugs@masanjin.net Tue Dec 14 03:05:01 2010
249 From: sup-bugs@masanjin.net (anonymous)
250 Date: Tue, 14 Dec 2010 08:05:01 +0000
251 Subject: [sup-devel] [issue138] Sup crash at startup
252 In-Reply-To: <1292313900.88.0.725708300725.issue138@masanjin.net>
253 Message-ID: <1292313900.88.0.725708300725.issue138@masanjin.net>
254
255
256 New submission from anonymous:
257
258 sup-mail crashes at startup. I can see the main screen but in half a second,
259 when not even the messages has appeared, it crashes:
260
261
262 --- RuntimeError from thread: load threads for thread-index-mode
263 wrong id called on nil
264 /usr/lib/ruby/1.8/sup.rb:16:in `id'
265 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:226:in `update'
266 /usr/lib/ruby/1.8/sup/hook.rb:122:in `sort_by'
267 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:226:in `each'
268 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:226:in `sort_by'
269 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:226:in `update'
270 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:224:in `synchronize'
271 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:224:in `update'
272 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:642:in
273 `__unprotected_load_n_threads'
274 (eval):12:in `load_n_threads'
275 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:614:in
276 `load_n_threads_background'
277 /usr/lib/ruby/1.8/sup.rb:76:in `reporting_thread'
278 /usr/lib/ruby/1.8/sup.rb:74:in `initialize'
279 /usr/lib/ruby/1.8/sup.rb:74:in `new'
280 /usr/lib/ruby/1.8/sup.rb:74:in `reporting_thread'
281 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:613:in
282 `load_n_threads_background'
283 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:684:in
284 `__unprotected_load_threads'
285 (eval):12:in `load_threads'
286 /usr/bin/sup-mail:224
287
288 ----------
289 files: sup-exception-log.txt
290 messages: 321
291 nosy: anonymous
292 priority: bug
293 ruby_version: 1.8.7
294 status: unread
295 sup_version: 0.10.2
296 title: Sup crash at startup
297
298 _________________________________________
299 Sup issue tracker <sup-bugs at masanjin.net>
300 <http://masanjin.net/sup-bugs/issue138>
301 _________________________________________
302 -------------- next part --------------
303 /usr/lib/ruby/1.8/monitor.rb:102:in `stop'
304 /usr/lib/ruby/1.8/monitor.rb:102:in `wait'
305 /usr/lib/ruby/1.8/net/imap.rb:974:in `get_tagged_response'
306 /usr/lib/ruby/1.8/net/imap.rb:1034:in `send_command'
307 /usr/lib/ruby/1.8/monitor.rb:242:in `synchronize'
308 /usr/lib/ruby/1.8/net/imap.rb:1019:in `send_command'
309 /usr/lib/ruby/1.8/net/imap.rb:1172:in `fetch_internal'
310 /usr/lib/ruby/1.8/monitor.rb:242:in `synchronize'
311 /usr/lib/ruby/1.8/net/imap.rb:1170:in `fetch_internal'
312 /usr/lib/ruby/1.8/net/imap.rb:713:in `fetch'
313 /usr/lib/ruby/1.8/sup/imap.rb:218:in `fetch'
314 /usr/lib/ruby/1.8/sup/imap.rb:332:in `safely'
315 /usr/lib/ruby/1.8/sup/imap.rb:218:in `fetch'
316 /usr/lib/ruby/1.8/sup/imap.rb:165:in `unsynchronized_scan_mailbox'
317 /usr/lib/ruby/1.8/sup/imap.rb:202:in `unsynchronized_start_offset'
318 (eval):3:in `start_offset'
319 (eval):3:in `synchronize'
320 (eval):3:in `start_offset'
321 /usr/lib/ruby/1.8/sup/source.rb:88:in `done?'
322 /usr/lib/ruby/1.8/sup/util.rb:599:in `send'
323 /usr/lib/ruby/1.8/sup/util.rb:599:in `__pass'
324 /usr/lib/ruby/1.8/sup/util.rb:586:in `method_missing'
325 /usr/lib/ruby/1.8/sup/poll.rb:155:in `each_message_from'
326 /usr/lib/ruby/1.8/sup/util.rb:559:in `send'
327 /usr/lib/ruby/1.8/sup/util.rb:559:in `method_missing'
328 /usr/bin/sup-sync:146
329 /usr/bin/sup-sync:141:in `each'
330 /usr/bin/sup-sync:141
331
332 From sup-bugs@masanjin.net Thu Dec 16 03:39:34 2010
333 From: sup-bugs@masanjin.net (anonymous)
334 Date: Thu, 16 Dec 2010 08:39:34 +0000
335 Subject: [sup-devel] [issue139] bug while deleting a message
336 In-Reply-To: <1292488774.0.0.532674457502.issue139@masanjin.net>
337 Message-ID: <1292488774.0.0.532674457502.issue139@masanjin.net>
338
339
340 New submission from anonymous:
341
342 while I was deleting a message from the inbox sup crashes..
343
344 ----------
345 files: exception-log.txt
346 messages: 324
347 nosy: anonymous
348 priority: bug
349 ruby_version: 1.9.1
350 status: unread
351 sup_version: git
352 title: bug while deleting a message
353
354 _________________________________________
355 Sup issue tracker <sup-bugs at masanjin.net>
356 <http://masanjin.net/sup-bugs/issue139>
357 _________________________________________
358 -------------- next part --------------
359 --- Errno::ENOSPC from thread: load messages for thread-view-mode
360 No space left on device - /tmp/redwood.payload20101216-29861-1v6uapo-0
361 /usr/lib/ruby/gems/1.9.1/gems/sup-999/lib/sup/crypto.rb:124:in `verify'
362 /usr/lib/ruby/gems/1.9.1/gems/sup-999/lib/sup/util.rb:609:in `method_missing'
363 /usr/lib/ruby/gems/1.9.1/gems/sup-999/lib/sup/message.rb:381:in `multipart_signed_to_chunks'
364 /usr/lib/ruby/gems/1.9.1/gems/sup-999/lib/sup/message.rb:421:in `message_to_chunks'
365 /usr/lib/ruby/gems/1.9.1/gems/sup-999/lib/sup/message.rb:259:in `load_from_source!'
366 /usr/lib/ruby/gems/1.9.1/gems/sup-999/lib/sup/modes/thread-index-mode.rb:116:in `block (3 levels) in select'
367 /usr/lib/ruby/gems/1.9.1/gems/sup-999/lib/sup/thread.rb:81:in `block (2 levels) in each'
368 /usr/lib/ruby/gems/1.9.1/gems/sup-999/lib/sup/thread.rb:176:in `block (2 levels) in each_with_stuff'
369 /usr/lib/ruby/gems/1.9.1/gems/sup-999/lib/sup/thread.rb:174:in `each_with_stuff'
370 /usr/lib/ruby/gems/1.9.1/gems/sup-999/lib/sup/thread.rb:176:in `block in each_with_stuff'
371 /usr/lib/ruby/gems/1.9.1/gems/sup-999/lib/sup/thread.rb:175:in `each'
372 /usr/lib/ruby/gems/1.9.1/gems/sup-999/lib/sup/thread.rb:175:in `each_with_stuff'
373 /usr/lib/ruby/gems/1.9.1/gems/sup-999/lib/sup/thread.rb:78:in `block in each'
374 /usr/lib/ruby/gems/1.9.1/gems/sup-999/lib/sup/thread.rb:75:in `each'
375 /usr/lib/ruby/gems/1.9.1/gems/sup-999/lib/sup/thread.rb:75:in `each'
376 /usr/lib/ruby/gems/1.9.1/gems/sup-999/lib/sup/modes/thread-index-mode.rb:113:in `each_with_index'
377 /usr/lib/ruby/gems/1.9.1/gems/sup-999/lib/sup/modes/thread-index-mode.rb:113:in `block (2 levels) in select'
378 /usr/lib/ruby/gems/1.9.1/gems/sup-999/lib/sup/buffer.rb:740:in `say'
379 /usr/lib/ruby/gems/1.9.1/gems/sup-999/lib/sup/util.rb:609:in `method_missing'
380 /usr/lib/ruby/gems/1.9.1/gems/sup-999/lib/sup/modes/thread-index-mode.rb:112:in `block in select'
381 /usr/lib/ruby/gems/1.9.1/gems/sup-999/lib/sup.rb:78:in `block in reporting_thread'
382
383 From tero@tilus.net Tue Dec 21 16:45:14 2010
384 From: tero@tilus.net (Tero Tilus)
385 Date: Tue, 21 Dec 2010 23:45:14 +0200
386 Subject: [sup-devel] Message#text_to_chunks performance
387 In-Reply-To: <1288264300-sup-7747@tilus.net>
388 References: <1288264300-sup-7747@tilus.net>
389 Message-ID: <1292967783-sup-4582@tilus.net>
390
391 And here's (finally) the patch.
392
393 --
394 Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
395 -------------- next part --------------
396 A non-text attachment was scrubbed...
397 Name: 0001-Message-text_to_chunks-avoid-O-n-2-behavior-on-seq.patch
398 Type: application/octet-stream
399 Size: 1266 bytes
400 Desc: not available
401 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20101221/da87abd5/attachment.obj>
402
403 From rlane@club.cc.cmu.edu Thu Dec 23 13:38:24 2010
404 From: rlane@club.cc.cmu.edu (Rich Lane)
405 Date: Thu, 23 Dec 2010 13:38:24 -0500
406 Subject: [sup-devel] Message#text_to_chunks performance
407 In-Reply-To: <1292967783-sup-4582@tilus.net>
408 References: <1288264300-sup-7747@tilus.net> <1292967783-sup-4582@tilus.net>
409 Message-ID: <1293129445-sup-8097@zyrg.net>
410
411 Branch blank-lines-perf, merged to next. I'll merge it to master after
412 0.12 is released.
413
414 From rlane@club.cc.cmu.edu Thu Dec 23 13:43:45 2010
415 From: rlane@club.cc.cmu.edu (Rich Lane)
416 Date: Thu, 23 Dec 2010 13:43:45 -0500
417 Subject: [sup-devel] [PATCH] Converted crypto to use the gpgme gem
418 In-Reply-To: <AANLkTi=AJZGLAra20fQvEvU0EasQ_1yWpsr6+4TV3iEn@mail.gmail.com>
419 References: <AANLkTinrSAheJb2F4Xw9AmgXcGLxeQh0_MEnuTSATye_@mail.gmail.com>
420 <AANLkTinXwKiJqgKyFrrcVV21a8j8hV=fw4QcvDLhtM8E@mail.gmail.com>
421 <AANLkTi=7yasVvAW4P85v3GJxf+quJrE3-1XruDgUZq+D@mail.gmail.com>
422 <1289466286-sup-7540@meteor.durcheinandertal.local>
423 <AANLkTikUwyX6xj-f_ZnLp6s2s9vaCpgayPKygniWndoJ@mail.gmail.com>
424 <1289907535-sup-3989@meteor.durcheinandertal.local>
425 <AANLkTi=xz16ecZ0C5=RUcOG4wzojVVzs70PZ2ueKa0ht@mail.gmail.com>
426 <1289932061-sup-96@meteor.durcheinandertal.local>
427 <AANLkTin=1MRrW0vuj_7uMvjcyLc3Aaw4ddZ_Rq6TBiyx@mail.gmail.com>
428 <AANLkTinvv59bWu0UfjW2K-xDRUP42tDwmgMh5yZdmaN_@mail.gmail.com>
429 <1291023322-sup-8457@meteor.durcheinandertal.local>
430 <AANLkTi=AJZGLAra20fQvEvU0EasQ_1yWpsr6+4TV3iEn@mail.gmail.com>
431 Message-ID: <1293129774-sup-3146@zyrg.net>
432
433 All 5 patches applied to branch gpgme and merged to next.
434
435 From sup-bugs@masanjin.net Sat Dec 25 11:50:56 2010
436 From: sup-bugs@masanjin.net (Matthias Vallentin)
437 Date: Sat, 25 Dec 2010 16:50:56 +0000
438 Subject: [sup-devel] [issue140] Execute startup hook before adding draft and
439 sent sources
440 In-Reply-To: <1293295856.45.0.529523964282.issue140@masanjin.net>
441 Message-ID: <1293295856.45.0.529523964282.issue140@masanjin.net>
442
443
444 New submission from Matthias Vallentin <vallentin at icir.org>:
445
446 By moving the execution of the startup hook before the selection of the draft and
447 send source, this hook becomes more flexible and allows users to have more control
448 about the source selection process.
449
450 Attached is a patch that enables this functionality.
451
452 ----------
453 files: hook.diff
454 messages: 341
455 nosy: matthias
456 priority: feature request
457 ruby_version: 1.8
458 status: unread
459 sup_version: git
460 title: Execute startup hook before adding draft and sent sources
461
462 _________________________________________
463 Sup issue tracker <sup-bugs at masanjin.net>
464 <http://masanjin.net/sup-bugs/issue140>
465 _________________________________________
466 -------------- next part --------------
467 diff --git a/bin/sup b/bin/sup
468 old mode 100755
469 new mode 100644
470 index 10be161..831964b
471 --- a/bin/sup
472 +++ b/bin/sup
473 @@ -158,6 +158,9 @@ begin
474 trap("TERM") { |x| $die = true }
475 trap("WINCH") { |x| BufferManager.sigwinch_happened! }
476
477 + HookManager.run "startup"
478 + Redwood::Keymap.run_hook global_keymap
479 +
480 if(s = Redwood::SourceManager.source_for DraftManager.source_name)
481 DraftManager.source = s
482 else
483 @@ -171,9 +174,6 @@ begin
484 Redwood::SourceManager.add_source SentManager.default_source
485 end
486
487 - HookManager.run "startup"
488 - Redwood::Keymap.run_hook global_keymap
489 -
490 debug "starting curses"
491 Redwood::Logger.remove_sink $stderr
492 start_cursing
493 diff --git a/bin/sup-add b/bin/sup-add
494 old mode 100755
495 new mode 100644
496 diff --git a/bin/sup-cmd b/bin/sup-cmd
497 old mode 100755
498 new mode 100644
499 diff --git a/bin/sup-config b/bin/sup-config
500 old mode 100755
501 new mode 100644
502 diff --git a/bin/sup-dump b/bin/sup-dump
503 old mode 100755
504 new mode 100644
505 diff --git a/bin/sup-recover-sources b/bin/sup-recover-sources
506 old mode 100755
507 new mode 100644
508 diff --git a/bin/sup-sync b/bin/sup-sync
509 old mode 100755
510 new mode 100644
511 diff --git a/bin/sup-sync-back b/bin/sup-sync-back
512 old mode 100755
513 new mode 100644
514 diff --git a/bin/sup-sync-back-maildir b/bin/sup-sync-back-maildir
515 old mode 100755
516 new mode 100644
517 diff --git a/bin/sup-tweak-labels b/bin/sup-tweak-labels
518 old mode 100755
519 new mode 100644
520
521 From tero@tilus.net Thu Dec 30 18:35:56 2010
522 From: tero@tilus.net (Tero Tilus)
523 Date: Fri, 31 Dec 2010 01:35:56 +0200
524 Subject: [sup-devel] Scrolling (with patches)
525 Message-ID: <1293750761-sup-3852@tilus.net>
526
527 Jonas H. reported about slow horizontal scrolling on talk.
528 http://rubyforge.org/pipermail/sup-talk/2010-December/004400.html
529
530 I looked into it and found out that scrolling is pretty much fully
531 dependant on Buffer#write and main cpu hogs within it are
532 String#display_length (uses String#scan when on 1.8) and
533 Ncurses::WINDOW#method_missing (wide/normal dispatching).
534
535 Caching String#display_length cuts down String#scan calls by ~30%.
536 That and hardwiring Ncurses::WINDOW#mvaddstr and #attrset cut average
537 Buffer#write call to half of what it was.
538
539 Also having configurable COL_JUMP would help people who need to scroll
540 horizontally a lot. Included in the sup patch.
541
542 Perceivable difference of these modifications is very small, at least
543 to me. Please have a look if these patches (one of them against sup
544 and another against ncursesw.rb in ncursesw gem) make any sense.
545
546 ====
547 --- /usr/lib/ruby/gems/1.8/gems/ncursesw-1.2.4.2/lib/ncursesw.rb 2010-12-
548 31 00:37:31.000000000 +0200
549 +++ lib/ncurses.rb 2010-12-30 23:50:26.000000000 +0200
550 @@ -59,6 +58,29 @@
551 module Destroy_checker; def destroyed?; @destroyed; end; end
552 class WINDOW
553 include Destroy_checker
554 +
555 + @@mvwaddstr = Ncurses.respond_to? "mvwaddstr"
556 + # This would be handled by #method_missing below, but for
557 + # performance reasons it is extracted here. #mvaddstr is the beef
558 + # of Redwood::Buffer#write which does all the drawing.
559 + def mvaddstr(*args)
560 + if @@mvwaddstr
561 + Ncurses.mvwaddstr(*args)
562 + else
563 + Ncurses.mvaddstr(*args)
564 + end
565 + end
566 +
567 + @@wattrset = Ncurses.respond_to? "wattrset"
568 + # See #mvaddstr abowe.
569 + def attrset(*args)
570 + if @@wattrset
571 + Ncurses.wattrset(*args)
572 + else
573 + Ncurses.attrset(*args)
574 + end
575 + end
576 +
577 def method_missing(name, *args)
578 name = name.to_s
579 if (name[0,2] == "mv")
580 ====
581
582 --
583 Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
584 -------------- next part --------------
585 A non-text attachment was scrubbed...
586 Name: 0002-Performance-and-configurability-of-horizontal-scroll.patch
587 Type: application/octet-stream
588 Size: 2673 bytes
589 Desc: not available
590 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20101231/bc945134/attachment-0001.obj>
591
592 From rlane@club.cc.cmu.edu Thu Dec 30 19:10:06 2010
593 From: rlane@club.cc.cmu.edu (Rich Lane)
594 Date: Thu, 30 Dec 2010 19:10:06 -0500
595 Subject: [sup-devel] Scrolling (with patches)
596 In-Reply-To: <1293750761-sup-3852@tilus.net>
597 References: <1293750761-sup-3852@tilus.net>
598 Message-ID: <1293753763-sup-6661@zyrg.net>
599
600 Yeah, I've noticed how slow method_missing is and that's also a problem
601 with our use of Singleton in the codebase. Here we might as well hoist
602 the conditional out of the method definition.
603
604 From tero@tilus.net Thu Dec 30 19:34:09 2010
605 From: tero@tilus.net (Tero Tilus)
606 Date: Fri, 31 Dec 2010 02:34:09 +0200
607 Subject: [sup-devel] Scrolling (with patches)
608 In-Reply-To: <1293753763-sup-6661@zyrg.net>
609 References: <1293750761-sup-3852@tilus.net> <1293753763-sup-6661@zyrg.net>
610 Message-ID: <1293755445-sup-9811@tilus.net>
611
612 Rich Lane, 2010-12-31 02:10:
613 > Yeah, I've noticed how slow method_missing is and that's also a
614 > problem with our use of Singleton in the codebase.
615
616 I think we could have Singleton.method_missing actually create the
617 methods as they are called.
618
619 --
620 Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
621
622 From tero@tilus.net Thu Dec 30 20:44:36 2010
623 From: tero@tilus.net (Tero Tilus)
624 Date: Fri, 31 Dec 2010 03:44:36 +0200
625 Subject: [sup-devel] Scrolling (with patches)
626 In-Reply-To: <1293755445-sup-9811@tilus.net>
627 References: <1293750761-sup-3852@tilus.net> <1293753763-sup-6661@zyrg.net>
628 <1293755445-sup-9811@tilus.net>
629 Message-ID: <1293759788-sup-1949@tilus.net>
630
631 Tero Tilus, 2010-12-31 02:34:
632 > I think we could have Singleton.method_missing actually create the
633 > methods as they are called.
634
635 >From words to deeds. ;)
636
637 --
638 Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
639 -------------- next part --------------
640 A non-text attachment was scrubbed...
641 Name: 0003-Improve-Singleton-performance.patch
642 Type: application/octet-stream
643 Size: 972 bytes
644 Desc: not available
645 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20101231/7ce5578e/attachment.obj>
646
647 From tero@tilus.net Thu Dec 30 22:18:29 2010
648 From: tero@tilus.net (Tero Tilus)
649 Date: Fri, 31 Dec 2010 05:18:29 +0200
650 Subject: [sup-devel] Scrolling (with patches)
651 In-Reply-To: <1293759788-sup-1949@tilus.net>
652 References: <1293750761-sup-3852@tilus.net> <1293753763-sup-6661@zyrg.net>
653 <1293755445-sup-9811@tilus.net> <1293759788-sup-1949@tilus.net>
654 Message-ID: <1293765315-sup-8280@tilus.net>
655
656 Tero Tilus, 2010-12-31 03:44:
657 > From words to deeds. ;)
658
659 ...to first fix. Private methods (at least Index.sync_message) are
660 being called on singletons and looks like they are expected to work.
661
662 --
663 Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
664 -------------- next part --------------
665 A non-text attachment was scrubbed...
666 Name: 0003-Improve-Singleton-performance.patch
667 Type: application/octet-stream
668 Size: 984 bytes
669 Desc: not available
670 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20101231/da0a3712/attachment.obj>
671
672 From sup-bugs@masanjin.net Fri Dec 31 05:03:36 2010
673 From: sup-bugs@masanjin.net (Jonas H)
674 Date: Fri, 31 Dec 2010 10:03:36 +0000
675 Subject: [sup-devel] [issue141] Can't see my own messages from Thunderbird
676 mbox sources
677 In-Reply-To: <1293789816.3.0.27954195476.issue141@masanjin.net>
678 Message-ID: <1293789816.3.0.27954195476.issue141@masanjin.net>
679
680
681 New submission from Jonas H <jonas at lophus.org>:
682
683 As discussed in this thread <http://rubyforge.org/pipermail/sup-talk/2010-
684 December/004387.html>, here comes my example mbox file.
685
686 The mbox attached contains two messages: One message to myself and one reply to
687 that message.
688
689 Short trip into the weird world of Thunderbird Disk Space Saving(tm):
690 If I got messages in folder A and then copy them to folder B, they won't really
691 be copied to save disk space. Thus, if I index folder B, all messages that were
692 copied from folder A are missing from the index. (If folder A gets deleted,
693 Thunderbird moves all marked-to-copy-into-B messages into folder B.)
694
695 In case of two messages, folder A actually contained three messages (although I
696 only see two of them in Thunderbird). The third message was the first e-mail I
697 sent to myself coming from the e-mail server - actually I immediately deleted
698 that one, but apparently it stays in the mbox anyway.
699
700 The mbox I attached is of type B, i.e. a folder that theoretically should
701 contain three messages following Thunderbird Logic(tm), but it only contains two
702 because Thunderbird does this magic disk space saving thing (I guess).
703
704 Anyway, sup should grab the bodies in both cases because they're in the mbox in
705 any case.
706
707 ----------
708 files: bla
709 messages: 363
710 nosy: jonash
711 priority: bug
712 ruby_version: 1.8
713 status: unread
714 sup_version: 0.11
715 title: Can't see my own messages from Thunderbird mbox sources
716
717 _________________________________________
718 Sup issue tracker <sup-bugs at masanjin.net>
719 <http://masanjin.net/sup-bugs/issue141>
720 _________________________________________
721 -------------- next part --------------
722 A non-text attachment was scrubbed...
723 Name: bla
724 Type: application/octet-stream
725 Size: 2572 bytes
726 Desc: not available
727 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20101231/77f59659/attachment.obj>
728