community/pipermail-archives/sup-devel/2011-03.txt (46266B) - raw
1 From dmishd@gmail.com Tue Mar 1 14:38:38 2011
2 From: dmishd@gmail.com (Hamish)
3 Date: Tue, 01 Mar 2011 19:38:38 +0000
4 Subject: [sup-devel] sup-server revisited
5 In-Reply-To: <1298762120-sup-1118@masanjin.net>
6 References: <1298320404-sup-5972@masanjin.net> <1298744738-sup-631@whisper>
7 <1298757625-sup-9756@masanjin.net>
8 <1298762120-sup-1118@masanjin.net>
9 Message-ID: <1299008245-sup-5110@whisper>
10
11 Excerpts from William Morgan's message of Sat Feb 26 23:15:50 +0000 2011:
12 > Reformatted excerpts from William Morgan's message of 2011-02-26:
13 > > I'm about to push some changes to Heliotrope that should make it easy to get
14 > > started with. I will announce here.
15 >
16 > Check out the README and see if the instructions work for you.
17
18 They do indeed, thank you. It's fun to play about with. I look forward
19 to watching it develop and hopefully contributing :)
20
21 Hamish Downer
22
23 From gregor@hoffleit.de Wed Mar 2 07:43:51 2011
24 From: gregor@hoffleit.de (Gregor Hoffleit)
25 Date: Wed, 02 Mar 2011 13:43:51 +0100
26 Subject: [sup-devel] sup-server revisited
27 In-Reply-To: <1299008245-sup-5110@whisper>
28 References: <1298320404-sup-5972@masanjin.net> <1298744738-sup-631@whisper>
29 <1298757625-sup-9756@masanjin.net>
30 <1298762120-sup-1118@masanjin.net> <1299008245-sup-5110@whisper>
31 Message-ID: <1299062215-sup-8517@sam.mediasupervision.de>
32
33 I keep getting stalls from the heliotrope-server process.
34
35 When adding a certain mbox file, the server reproducably hangs after
36 1167 messages, leading to an RestClient::RequestTimeout exception in
37 heliotrope-add.
38
39 At this point I have to kill -KILL the heliotrope-server process.
40
41 I can't give away the mbox file. Any hints how I could debug the
42 heliotrope-server script?
43
44
45 Nice work otherwise! The web client is a nice demonstration of what
46 might come out of this project ;-)
47
48 Gregor
49
50
51
52 * Hamish <dmishd at gmail.com> [Di M?r 01 20:38:38 +0100 2011]
53 > Excerpts from William Morgan's message of Sat Feb 26 23:15:50 +0000 2011:
54 > > Reformatted excerpts from William Morgan's message of 2011-02-26:
55 > > > I'm about to push some changes to Heliotrope that should make it easy to get
56 > > > started with. I will announce here.
57 > >
58 > > Check out the README and see if the instructions work for you.
59 >
60 > They do indeed, thank you. It's fun to play about with. I look forward
61 > to watching it develop and hopefully contributing :)
62
63 From wmorgan-sup@masanjin.net Wed Mar 2 13:51:58 2011
64 From: wmorgan-sup@masanjin.net (William Morgan)
65 Date: Wed, 02 Mar 2011 18:51:58 +0000
66 Subject: [sup-devel] sup-server revisited
67 In-Reply-To: <1299062215-sup-8517@sam.mediasupervision.de>
68 References: <1298320404-sup-5972@masanjin.net> <1298744738-sup-631@whisper>
69 <1298757625-sup-9756@masanjin.net>
70 <1298762120-sup-1118@masanjin.net> <1299008245-sup-5110@whisper>
71 <1299062215-sup-8517@sam.mediasupervision.de>
72 Message-ID: <1299091467-sup-7084@masanjin.net>
73
74 Reformatted excerpts from Gregor Hoffleit's message of 2011-03-02:
75 > I can't give away the mbox file. Any hints how I could debug the
76 > heliotrope-server script?
77
78 Can you isolate the message? It might be that it has a huge attachment
79 that RMail is taking forever to parse, and that results in a client
80 timeout.
81
82 I need to move the message processing out of the request loop,
83 obviously.
84
85 As a workaround (which also is much faster), kill the server, wipe
86 everything, and use `heliotrope-add -d <dir>` to import an mbox or
87 maildir without having to go through HTTP.
88
89 > Nice work otherwise! The web client is a nice demonstration of what
90 > might come out of this project ;-)
91
92 Thanks! I'm currently working on stripping everything out of Sup that
93 will be handled by the server. The good news is that this is a LOT, and
94 that Sup will be much leaner and meaner than before.
95 --
96 William <wmorgan-sup at masanjin.net>
97
98 From gregor@hoffleit.de Thu Mar 3 12:32:34 2011
99 From: gregor@hoffleit.de (Gregor Hoffleit)
100 Date: Thu, 03 Mar 2011 18:32:34 +0100
101 Subject: [sup-devel] sup-server revisited
102 In-Reply-To: <1299091467-sup-7084@masanjin.net>
103 References: <1298320404-sup-5972@masanjin.net> <1298744738-sup-631@whisper>
104 <1298757625-sup-9756@masanjin.net>
105 <1298762120-sup-1118@masanjin.net> <1299008245-sup-5110@whisper>
106 <1299062215-sup-8517@sam.mediasupervision.de>
107 <1299091467-sup-7084@masanjin.net>
108 Message-ID: <1299172989-sup-8183@sam.mediasupervision.de>
109
110 William, I was able to isolate my problem: For me, heliotrope-add hangs
111 for messages with more than 32768 content lines.
112
113 I have attached two mbox files, each containing a single message.
114 The message in good.mbox has 32768 content lines (excluding header) and
115 has no problem in heliotrope-add. The message in bad.mbox has 32769
116 content lines, and heliotrope-add hangs when trying to add this message.
117
118 I haven't yet tried to locate the locate the problem in the source.
119
120 Regards,
121 Gregor
122
123
124 * William Morgan <wmorgan-sup at masanjin.net> [Mi M?r 02 19:51:58 +0100 2011]
125 > Reformatted excerpts from Gregor Hoffleit's message of 2011-03-02:
126 > > I can't give away the mbox file. Any hints how I could debug the
127 > > heliotrope-server script?
128 >
129 > Can you isolate the message? It might be that it has a huge attachment
130 > that RMail is taking forever to parse, and that results in a client
131 > timeout.
132 >
133 > I need to move the message processing out of the request loop,
134 > obviously.
135 >
136 > As a workaround (which also is much faster), kill the server, wipe
137 > everything, and use `heliotrope-add -d <dir>` to import an mbox or
138 > maildir without having to go through HTTP.
139 >
140 > > Nice work otherwise! The web client is a nice demonstration of what
141 > > might come out of this project ;-)
142 >
143 > Thanks! I'm currently working on stripping everything out of Sup that
144 > will be handled by the server. The good news is that this is a LOT, and
145 > that Sup will be much leaner and meaner than before.
146 -------------- next part --------------
147 A non-text attachment was scrubbed...
148 Name: mbox-32768lines.tar.gz
149 Type: application/x-gzip
150 Size: 804 bytes
151 Desc: not available
152 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20110303/27c79630/attachment.gz>
153
154 From wmorgan-sup@masanjin.net Thu Mar 3 14:17:36 2011
155 From: wmorgan-sup@masanjin.net (William Morgan)
156 Date: Thu, 03 Mar 2011 19:17:36 +0000
157 Subject: [sup-devel] sup-server revisited
158 In-Reply-To: <1299172989-sup-8183@sam.mediasupervision.de>
159 References: <1298320404-sup-5972@masanjin.net> <1298744738-sup-631@whisper>
160 <1298757625-sup-9756@masanjin.net>
161 <1298762120-sup-1118@masanjin.net> <1299008245-sup-5110@whisper>
162 <1299062215-sup-8517@sam.mediasupervision.de>
163 <1299091467-sup-7084@masanjin.net>
164 <1299172989-sup-8183@sam.mediasupervision.de>
165 Message-ID: <1299179837-sup-4675@masanjin.net>
166
167 Reformatted excerpts from Gregor Hoffleit's message of 2011-03-03:
168 > William, I was able to isolate my problem: For me, heliotrope-add hangs
169 > for messages with more than 32768 content lines.
170
171 Crazy! I will take a look. Thanks for the good debugging.
172 --
173 William <wmorgan-sup at masanjin.net>
174
175 From sascha-ml-reply-to-2011-2@silbe.org Thu Mar 3 14:38:14 2011
176 From: sascha-ml-reply-to-2011-2@silbe.org (Sascha Silbe)
177 Date: Thu, 03 Mar 2011 20:38:14 +0100
178 Subject: [sup-devel] sup-server revisited
179 In-Reply-To: <1298485426-sup-5530@masanjin.net>
180 References: <1298320404-sup-5972@masanjin.net> <1298400274-sup-4941@tilus.net>
181 <1298409714-sup-1926@masanjin.net>
182 <4d64d7dc.5989cc0a.4550.ffffb543@mx.google.com>
183 <1298485426-sup-5530@masanjin.net>
184 Message-ID: <1299179944-sup-5017@xo15-sascha.sascha.silbe.org>
185
186 Excerpts from William Morgan's message of Wed Feb 23 19:43:34 +0100 2011:
187
188 > - Individual messages have "state", including unread, starred, and all the
189 > other things you've mentioned.
190
191 Are you going to support user-defined "states"? I have quite a few
192 labels that would make much more sense on the message than on the thread
193 (e.g. todo-{low,normal,high}).
194
195 I sometimes "reply" to messages without setting a recipient in order to
196 record private notes. It would be nice if this capability was either
197 preserved (i.e. don't choke if there's no recipient) or maybe even
198 explicit support for non-mail objects (notes, attached files, reminder
199 dates, etc.) added.
200
201 > - The user can set the labels for a thread, but can't create labels that have
202 > the same name as a message state.
203
204 Hmm, that has a chance of conflicting with user-defined message states...
205
206 Sascha
207
208 --
209 http://sascha.silbe.org/
210 http://www.infra-silbe.de/
211 -------------- next part --------------
212 A non-text attachment was scrubbed...
213 Name: signature.asc
214 Type: application/pgp-signature
215 Size: 494 bytes
216 Desc: not available
217 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20110303/4b54cbb9/attachment.bin>
218
219 From damien.leone@fensalir.fr Fri Mar 4 04:05:52 2011
220 From: damien.leone@fensalir.fr (Damien Leone)
221 Date: Fri, 04 Mar 2011 10:05:52 +0100
222 Subject: [sup-devel] call for new maintainers
223 In-Reply-To: <1296054871-sup-9586@masanjin.net>
224 References: <1295894044-sup-7965@masanjin.net>
225 <1295896722-sup-5870@midna.zekjur.net>
226 <1296054871-sup-9586@masanjin.net>
227 Message-ID: <1299229478-sup-2055@mailer>
228
229 Hello,
230
231 Could I have an access so I can push the finished maildir-sync branch
232 as well as some other patches?
233
234 My gitorious login is dleone.
235
236 Thanks,
237
238 Excerpts from William Morgan's message of mer. janv. 26 16:18:59 +0100 2011:
239 > Reformatted excerpts from Michael Stapelberg's message of 2011-01-24:
240 > > I don?t have enough time to be the only person doing this, but I do
241 > > offer my help on reviewing/merging patches. Maybe having more than one
242 > > guy with commit access turns out to be a good thing?
243 >
244 > Yeah, maybe that's the right idea.
245 >
246 > So let's try this. Michael, Tero, Sascha, Edward, and everyone else
247 > who's had code make it into Sup successfully... if you send me your
248 > Gitorious usernames, I will add you to the Sup group and you will have
249 > push access. Then you can bypass the list mailing list for patches
250 > entirely, which will save me a lot of work.
251 >
252 > All I ask is that you divide things into nice topic branches and merge
253 > them into next but not master. I'll merge individual branches into
254 > master when prepping for a release.
255
256 --
257 Damien Leone <damien.leone at fensalir.fr>
258
259 Web: http://dleone.fensalir.fr/
260 GPG: 0x82EB4DDF
261
262 From sascha-ml-reply-to-2011-2@silbe.org Fri Mar 4 07:16:41 2011
263 From: sascha-ml-reply-to-2011-2@silbe.org (Sascha Silbe)
264 Date: Fri, 04 Mar 2011 13:16:41 +0100
265 Subject: [sup-devel] call for new maintainers
266 In-Reply-To: <1296054871-sup-9586@masanjin.net>
267 References: <1295894044-sup-7965@masanjin.net>
268 <1295896722-sup-5870@midna.zekjur.net>
269 <1296054871-sup-9586@masanjin.net>
270 Message-ID: <1299240549-sup-530@xo15-sascha.sascha.silbe.org>
271
272 Excerpts from William Morgan's message of Wed Jan 26 16:18:59 +0100 2011:
273
274 > So let's try this. Michael, Tero, Sascha, Edward, and everyone else
275 > who's had code make it into Sup successfully... if you send me your
276 > Gitorious usernames, I will add you to the Sup group and you will have
277 > push access.
278
279 I've finally created a gitorious account. I don't quite like the wording
280 of the ToS [1] concerning licenses (the way I read it Gitorious AS is
281 allowed to redistribute my code using a proprietary license), but
282 then the sup repository with all my submitted patches already is hosted
283 by them...
284
285 > Then you can bypass the list mailing list for patches
286 > entirely, which will save me a lot of work.
287
288 I'm happy to push my patches, but I'd still prefer to get at least one
289 Reviewed-By to make sure my changes are kosher.
290
291 > All I ask is that you divide things into nice topic branches and merge
292 > them into next but not master. I'll merge individual branches into
293 > master when prepping for a release.
294
295 Noted.
296
297 Sascha
298
299 [1] http://en.gitorious.org/tos/
300 --
301 http://sascha.silbe.org/
302 http://www.infra-silbe.de/
303 -------------- next part --------------
304 A non-text attachment was scrubbed...
305 Name: signature.asc
306 Type: application/pgp-signature
307 Size: 494 bytes
308 Desc: not available
309 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20110304/99d68da8/attachment.bin>
310
311 From sascha-ml-reply-to-2011-2@silbe.org Fri Mar 4 07:19:03 2011
312 From: sascha-ml-reply-to-2011-2@silbe.org (Sascha Silbe)
313 Date: Fri, 04 Mar 2011 13:19:03 +0100
314 Subject: [sup-devel] call for new maintainers
315 In-Reply-To: <1299240549-sup-530@xo15-sascha.sascha.silbe.org>
316 References: <1295894044-sup-7965@masanjin.net>
317 <1295896722-sup-5870@midna.zekjur.net>
318 <1296054871-sup-9586@masanjin.net>
319 <1299240549-sup-530@xo15-sascha.sascha.silbe.org>
320 Message-ID: <1299241093-sup-4960@xo15-sascha.sascha.silbe.org>
321
322 Excerpts from Sascha Silbe's message of Fri Mar 04 13:16:41 +0100 2011:
323
324 > I've finally created a gitorious account.
325
326 And of course forgot to mention the account name: silbe.
327
328 Sascha
329
330 --
331 http://sascha.silbe.org/
332 http://www.infra-silbe.de/
333 -------------- next part --------------
334 A non-text attachment was scrubbed...
335 Name: signature.asc
336 Type: application/pgp-signature
337 Size: 494 bytes
338 Desc: not available
339 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20110304/c5d9c77d/attachment.bin>
340
341 From sup@zevv.nl Sun Mar 6 13:34:56 2011
342 From: sup@zevv.nl (Ico Doornekamp)
343 Date: Sun, 06 Mar 2011 19:34:56 +0100
344 Subject: [sup-devel] Mail-to-self does not end up in inbox
345 Message-ID: <1299436337-sup-4604@pruts.nl>
346
347 Hi all,
348
349 Back in the old days when using mutt, I regularly used to send mails to
350 myself as reminders or short notes. Sup however shows intelligent
351 behaviour, recognizes the message is both sent and received, and
352 attaches a 'sent' label to it, and thus the mail does not show up in the
353 inbox.
354
355 Is there a simple workaround for this ? Could this be considered a bug,
356 or is this just functioning as designed ?
357
358 Thanks,
359
360 Ico
361
362 --
363 :wq
364 ^X^Cy^K^X^C^C^C^C
365
366 From steve.goldman@gmail.com Sun Mar 6 14:15:29 2011
367 From: steve.goldman@gmail.com (Steve)
368 Date: Sun, 6 Mar 2011 14:15:29 -0500
369 Subject: [sup-devel] Mail-to-self does not end up in inbox
370 In-Reply-To: <1299436337-sup-4604@pruts.nl>
371 References: <1299436337-sup-4604@pruts.nl>
372 Message-ID: <AANLkTinhMkSpSR7FLO+hWc2TYgScrU0mikad4dsHaF+M@mail.gmail.com>
373
374 This is a bug to me. Although, if I recall, sup did not used to
375 behave this way. So likely someone thought the opposite was a bug.
376
377 On Sun, Mar 6, 2011 at 1:34 PM, Ico Doornekamp <sup at zevv.nl> wrote:
378 > Hi all,
379 >
380 > Back in the old days when using mutt, I regularly used to send mails to
381 > myself as reminders or short notes. Sup however shows intelligent
382 > behaviour, recognizes the message is both sent and received, and
383 > attaches a 'sent' label to it, and thus the mail does not show up in the
384 > inbox.
385 >
386 > Is there a simple workaround for this ? Could this be considered a bug,
387 > or is this just functioning as designed ?
388 >
389 > Thanks,
390 >
391 > Ico
392 >
393 > --
394 > :wq
395 > ^X^Cy^K^X^C^C^C^C
396 > _______________________________________________
397 > Sup-devel mailing list
398 > Sup-devel at rubyforge.org
399 > http://rubyforge.org/mailman/listinfo/sup-devel
400 >
401
402 From dmishd@gmail.com Sun Mar 6 18:36:24 2011
403 From: dmishd@gmail.com (Hamish)
404 Date: Sun, 06 Mar 2011 23:36:24 +0000
405 Subject: [sup-devel] Mail-to-self does not end up in inbox
406 In-Reply-To: <1299436337-sup-4604@pruts.nl>
407 References: <1299436337-sup-4604@pruts.nl>
408 Message-ID: <1299454258-sup-7115@whisper>
409
410 Excerpts from Ico Doornekamp's message of Sun Mar 06 18:34:56 +0000 2011:
411 > Back in the old days when using mutt, I regularly used to send mails to
412 > myself as reminders or short notes. Sup however shows intelligent
413 > behaviour, recognizes the message is both sent and received, and
414 > attaches a 'sent' label to it, and thus the mail does not show up in the
415 > inbox.
416 >
417 > Is there a simple workaround for this ? Could this be considered a bug,
418 > or is this just functioning as designed ?
419
420 I generally prefer sent email to not show up in the inbox - I try to
421 keep my inbox somewhere near zero (though I rarely achieve it ...)
422
423 A work around could be to add the inbox label to sent mail that is just
424 to you. In before-add-message.rb you could have something like:
425
426
427 if message.from.email == "me at mine.com" && message.to.length == 1 && message.to[0].email == "me at mine.com"
428 message.add_label :inbox
429 end
430
431
432 I haven't tested that, so you may want to check your logs if you try
433 using it. Or you could have a keyword in the subject - [ACTION] maybe -
434 and have a hook filter for that.
435
436 Hamish
437
438 From sup@zevv.nl Mon Mar 7 01:51:57 2011
439 From: sup@zevv.nl (Ico Doornekamp)
440 Date: Mon, 07 Mar 2011 07:51:57 +0100
441 Subject: [sup-devel] Mail-to-self does not end up in inbox
442 In-Reply-To: <1299454258-sup-7115@whisper>
443 References: <1299436337-sup-4604@pruts.nl> <1299454258-sup-7115@whisper>
444 Message-ID: <1299480660-sup-5856@pruts.nl>
445
446 * On Mon Mar 07 00:36:24 +0100 2011, Hamish wrote:
447
448 > Excerpts from Ico Doornekamp's message of Sun Mar 06 18:34:56 +0000 2011:
449 > > Back in the old days when using mutt, I regularly used to send mails to
450 > > myself as reminders or short notes. Sup however shows intelligent
451 > > behaviour, recognizes the message is both sent and received, and
452 > > attaches a 'sent' label to it, and thus the mail does not show up in the
453 > > inbox.
454 > >
455 > > Is there a simple workaround for this ? Could this be considered a bug,
456 > > or is this just functioning as designed ?
457 >
458 > I generally prefer sent email to not show up in the inbox - I try to
459 > keep my inbox somewhere near zero (though I rarely achieve it ...)
460 >
461 > A work around could be to add the inbox label to sent mail that is just
462 > to you. In before-add-message.rb you could have something like:
463 >
464 >
465 > if message.from.email == "me at mine.com" && message.to.length == 1 && message.to[0].email == "me at mine.com"
466 > message.add_label :inbox
467 > end
468 >
469 > I haven't tested that, so you may want to check your logs if you try
470 > using it.
471
472 Works like a charm. Thanks!
473
474 --
475 :wq
476 ^X^Cy^K^X^C^C^C^C
477
478 From aidecoe@aidecoe.name Mon Mar 7 03:27:56 2011
479 From: aidecoe@aidecoe.name (=?utf-8?q?Amadeusz_=C5=BBo=C5=82nowski?=)
480 Date: Mon, 07 Mar 2011 09:27:56 +0100
481 Subject: [sup-devel] Mail-to-self does not end up in inbox
482 In-Reply-To: <1299454258-sup-7115@whisper>
483 References: <1299436337-sup-4604@pruts.nl> <1299454258-sup-7115@whisper>
484 Message-ID: <1299486205-sup-2424@ittemni>
485
486 Excerpts from Hamish's message of Mon Mar 07 00:36:24 +0100 2011:
487 > Excerpts from Ico Doornekamp's message of Sun Mar 06 18:34:56 +0000 2011:
488 > > Back in the old days when using mutt, I regularly used to send mails to
489 > > myself as reminders or short notes. Sup however shows intelligent
490 > > behaviour, recognizes the message is both sent and received, and
491 > > attaches a 'sent' label to it, and thus the mail does not show up in the
492 > > inbox.
493 > >
494 > > Is there a simple workaround for this ? Could this be considered a bug,
495 > > or is this just functioning as designed ?
496 >
497 > I generally prefer sent email to not show up in the inbox - I try to
498 > keep my inbox somewhere near zero (though I rarely achieve it ...)
499 >
500 > A work around could be to add the inbox label to sent mail that is just
501 > to you. In before-add-message.rb you could have something like:
502 >
503 >
504 > if message.from.email == "me at mine.com" && message.to.length == 1 && message.to[0].email == "me at mine.com"
505 > message.add_label :inbox
506 > end
507
508 Why not have requested behaviour (sent mail in inbox) and hook for
509 archiving? E.g. I am usually modyfing labels on sent mail. And it's
510 easier to archive sent mail than unarchive it.
511 --
512 Amadeusz ?o?nowski
513
514 PGP key fpr: C700 CEDE 0C18 212E 49DA 4653 F013 4531 E1DB FAB5
515 -------------- next part --------------
516 A non-text attachment was scrubbed...
517 Name: signature.asc
518 Type: application/pgp-signature
519 Size: 490 bytes
520 Desc: not available
521 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20110307/06ea9644/attachment.bin>
522
523 From wmorgan-sup@masanjin.net Mon Mar 7 13:27:20 2011
524 From: wmorgan-sup@masanjin.net (William Morgan)
525 Date: Mon, 07 Mar 2011 18:27:20 +0000
526 Subject: [sup-devel] call for new maintainers
527 In-Reply-To: <1299229478-sup-2055@mailer>
528 References: <1295894044-sup-7965@masanjin.net>
529 <1295896722-sup-5870@midna.zekjur.net>
530 <1296054871-sup-9586@masanjin.net> <1299229478-sup-2055@mailer>
531 Message-ID: <1299522431-sup-5264@masanjin.net>
532
533 Reformatted excerpts from Damien Leone's message of 2011-03-04:
534 > My gitorious login is dleone.
535
536 Added.
537 --
538 William <wmorgan-sup at masanjin.net>
539
540 From wmorgan-sup@masanjin.net Mon Mar 7 13:27:38 2011
541 From: wmorgan-sup@masanjin.net (William Morgan)
542 Date: Mon, 07 Mar 2011 18:27:38 +0000
543 Subject: [sup-devel] call for new maintainers
544 In-Reply-To: <1299241093-sup-4960@xo15-sascha.sascha.silbe.org>
545 References: <1295894044-sup-7965@masanjin.net>
546 <1295896722-sup-5870@midna.zekjur.net>
547 <1296054871-sup-9586@masanjin.net>
548 <1299240549-sup-530@xo15-sascha.sascha.silbe.org>
549 <1299241093-sup-4960@xo15-sascha.sascha.silbe.org>
550 Message-ID: <1299522452-sup-1082@masanjin.net>
551
552 Reformatted excerpts from Sascha Silbe's message of 2011-03-04:
553 > And of course forgot to mention the account name: silbe.
554
555 Added.
556 --
557 William <wmorgan-sup at masanjin.net>
558
559 From damien.leone@fensalir.fr Mon Mar 7 16:22:50 2011
560 From: damien.leone@fensalir.fr (Damien Leone)
561 Date: Mon, 07 Mar 2011 22:22:50 +0100
562 Subject: [sup-devel] [PATCH] Mark the thread as read after the
563 ThreadViewMode has been instancied and displayed
564 In-Reply-To: <1298826320-sup-8596@mailer>
565 References: <1298826320-sup-8596@mailer>
566 Message-ID: <1299532949-sup-5258@mailer>
567
568 Pushed.
569
570 --
571 Damien Leone <damien.leone at fensalir.fr>
572
573 Web: http://dleone.fensalir.fr/
574 GPG: 0x82EB4DDF
575
576 From damien.leone@fensalir.fr Mon Mar 7 16:23:28 2011
577 From: damien.leone@fensalir.fr (Damien Leone)
578 Date: Mon, 07 Mar 2011 22:23:28 +0100
579 Subject: [sup-devel] [PATCH] line-cursor-mode: Add an option to disable
580 automatic threads loading when scrolling down for slow CPUs
581 In-Reply-To: <1298825716-sup-3818@mailer>
582 References: <1298825716-sup-3818@mailer>
583 Message-ID: <1299532993-sup-1598@mailer>
584
585 Pushed.
586
587 --
588 Damien Leone <damien.leone at fensalir.fr>
589
590 Web: http://dleone.fensalir.fr/
591 GPG: 0x82EB4DDF
592
593 From damien.leone@fensalir.fr Sun Mar 13 12:13:05 2011
594 From: damien.leone@fensalir.fr (Damien Leone)
595 Date: Sun, 13 Mar 2011 17:13:05 +0100
596 Subject: [sup-devel] [PATCHES] Add an account selector in edit-mode
597 Message-ID: <1300032642-sup-9716@mailer>
598
599 Sup guys,
600
601 Please see commit messages for detailed informations.
602
603 --
604 Damien Leone <damien.leone at fensalir.fr>
605
606 Web: http://dleone.fensalir.fr/
607 GPG: 0x82EB4DDF
608 -------------- next part --------------
609 A non-text attachment was scrubbed...
610 Name: 0001-reply-mode-improve-the-way-headers-are-handled.patch
611 Type: application/octet-stream
612 Size: 5389 bytes
613 Desc: not available
614 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20110313/596a02ed/attachment-0003.obj>
615 -------------- next part --------------
616 A non-text attachment was scrubbed...
617 Name: 0002-edit-message-mode-Add-an-optional-account-selector.patch
618 Type: application/octet-stream
619 Size: 4018 bytes
620 Desc: not available
621 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20110313/596a02ed/attachment-0004.obj>
622 -------------- next part --------------
623 A non-text attachment was scrubbed...
624 Name: 0003-edit-message-mode-Fix-the-way-signatures-are-handled.patch
625 Type: application/octet-stream
626 Size: 3266 bytes
627 Desc: not available
628 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20110313/596a02ed/attachment-0005.obj>
629
630 From damien.leone@fensalir.fr Sun Mar 13 12:41:04 2011
631 From: damien.leone@fensalir.fr (Damien Leone)
632 Date: Sun, 13 Mar 2011 17:41:04 +0100
633 Subject: [sup-devel] Adding backward synchronization for Maildir sources
634 In-Reply-To: <1278693172-sup-6247@mailer>
635 References: <1278693172-sup-6247@mailer>
636 Message-ID: <1300032886-sup-4779@mailer>
637
638 Sup guys,
639
640 Sorry for having been so long.
641
642 What's new:
643
644 - I added an option in sup-sync-back-maildir to merge the :replied and
645 :forwarded labels/flags so the first time you run the script you
646 should not lose any information on the IMAP side;
647
648 - A way to detect if sup-sync-back-to-maildir should be executed in
649 order to synchronize your index back to the Maildir source in order to
650 prevent any loss of information. A magic file is written in the
651 configuration directory everytime the script is executed and it is
652 removed when the sync_back_to_maildir option is set from false to
653 true;
654
655 - I fixed a case when messages were not properly updated when they
656 were remotely modified.
657
658 I have pushed the last commits to the maildir-sync branch [0], it is
659 rebased from master. I also have a branch rebased from next on my own
660 repository if you'd rather a more up to date branch [1].
661
662 Please test and review! For more informations and a howto, read the
663 message quoted below this mail.
664
665 [0] http://gitorious.org/sup/mainline/commits/maildir-sync
666 [1] http://git.fensalir.fr/?p=dleone/sup.git
667
668 Excerpts from Damien Leone's message of ven. juil. 09 18:44:01 +0200 2010:
669 > Sup guys,
670 >
671 > I have been working on backward synchronization for Maildir sources
672 > last week and I need your help to test and review the code.
673 >
674 > I pushed my commits (based on the 'next' branch) to my repo which you
675 > can find here [0] for the web interface and here [1] for the git
676 > address.
677 >
678 > The following is related to Maildir sources ONLY.
679 >
680 > So what does work and what does not (if you don't want to read this,
681 > scroll to the quick howto below):
682 >
683 > - Sup will now stay synchronized with your remote sources by detecting
684 > if a message has been remotely updated (ie: you change a flag from
685 > another client), these updates will be applied to your local index and
686 > your thread-view-mode buffers should be properly refreshed;
687 >
688 > - When a message is remotely deleted, it should now disappear from
689 > your index;
690 >
691 > - There is a new configuration option called "sync_back_to_maildir"
692 > which is false by default. When true, this option updates your actual
693 > Maildir files when you change a label, this is done in real time
694 > before being saved to xapian. So for instance if you use offlineimap
695 > the changes should be synched back to your IMAP server by the next
696 > poll in Sup (assuming that your before-poll hook runs offlineimap);
697 >
698 > - I wrote a "sup-sync-back-maildir" script that will synchronize all
699 > messages from your sources at once. This should be executed the first
700 > time BEFORE any polling, otherwise your IMAP server will be synched to
701 > your Sup index and if you did not used another client to mark your
702 > emails as read etc. (like me) and to update your IMAP server then you
703 > will lose all what you did in Sup (labels, etc.);
704 >
705 > - I added two new hidden labels in Sup: 'replied' and 'forwarded',
706 > they are automatically added when replying, forwarding or bouncing a
707 > message, this is to bring a better Maildir support to Sup, this should
708 > be invisible for users;
709 >
710 > - However you will probably lose all your remote 'replied' and
711 > 'forwarded' flags after your first backward synchronization to Maildir
712 > since Sup dropped these labels when it added your messages to xapian.
713 >
714 > - Moving a message from a Maildir source to another is not (yet?)
715 > supported.
716 >
717 > So, you should now be able to use multiple clients to handle your
718 > emails, for instance I can use gmail to mark messages as starred or
719 > so, it will be reflected in Sup. In the same way, if I mark a message
720 > as read in Sup it will appear as read in the gmail web interface.
721 >
722 > I tested this code with my main account (2 GB and like 15 Maildir
723 > sources) it works fine so far.
724 >
725 > Be warned that it is highly experimental, but if you use offlineimap
726 > it has a realdelete option so you *should* not lose any email, in the
727 > worst case it might mess your flags/labels up.
728 >
729 > I tested it only with offlineimap working with a gmail account.
730 >
731 > Quick howto:
732 >
733 > 1. Close sup
734 > 2. Backup your emails and your xapian index or use another Sup session
735 > 3. Clone the branch [1]
736 > 4. IMPORTANT: run "bin/sup-sync-back-maildir" to synchronize the
737 > Maildirs you wish, check the help
738 > 5. Add ":sync_back_to_maildir: true" to your config.yaml
739 > 6. Run and use sup
740 >
741 > Please test it and make reviews! :)
742 >
743 > NOTE: if you want this to work, get sure that you are not calling
744 > offlineimap with the '-q' option (as suggested in the wiki) otherwise
745 > it will ignore the flag updates on IMAP server, so check your
746 > before-poll hook.
747 >
748 > [0] http://git.fensalir.fr/?p=dleone/sup.git
749 > [1] $ git clone git://fensalir.fr/dleone/sup.git -b maildir-sync
750 >
751
752 --
753 Damien Leone <damien.leone at fensalir.fr>
754
755 Web: http://dleone.fensalir.fr/
756 GPG: 0x82EB4DDF
757
758 From damien.leone@fensalir.fr Sun Mar 13 12:42:17 2011
759 From: damien.leone@fensalir.fr (Damien Leone)
760 Date: Sun, 13 Mar 2011 17:42:17 +0100
761 Subject: [sup-devel] [PATCH] Avoid O(n^2) complexity for maildir
762 deduplication.
763 In-Reply-To: <1295563453-31049-1-git-send-email-ezyang@mit.edu>
764 References: <1295563453-31049-1-git-send-email-ezyang@mit.edu>
765 Message-ID: <1300034524-sup-1251@mailer>
766
767 Pushed, thanks!
768
769 Excerpts from Edward Z. Yang's message of jeu. janv. 20 23:44:13 +0100 2011:
770 > Signed-off-by: Edward Z. Yang <ezyang at mit.edu>
771 > ---
772 > lib/sup/maildir.rb | 8 +++++---
773 > 1 files changed, 5 insertions(+), 3 deletions(-)
774 >
775 > diff --git a/lib/sup/maildir.rb b/lib/sup/maildir.rb
776 > index ba8efed..bc30baa 100644
777 > --- a/lib/sup/maildir.rb
778 > +++ b/lib/sup/maildir.rb
779 > @@ -128,14 +128,16 @@ class Maildir < Source
780 > ## deleted arrays, meaning that its flags changed or that it has
781 > ## been moved, these ids need to be removed from added and deleted
782 > add_to_delete = del_to_delete = []
783 > + map = Hash.new { |hash, key| hash[key] = [] }
784 > + deleted.each do |id_del|
785 > + map[maildir_data(id_del)[0]].push id_del
786 > + end
787 > added.each do |id_add|
788 > - deleted.each do |id_del|
789 > - if maildir_data(id_add)[0] == maildir_data(id_del)[0]
790 > + map[maildir_data(id_add)[0]].each do |id_del|
791 > updated.push [ id_del, id_add ]
792 > add_to_delete.push id_add
793 > del_to_delete.push id_del
794 > end
795 > - end
796 > end
797 > added -= add_to_delete
798 > deleted -= del_to_delete
799
800 --
801 Damien Leone <damien.leone at fensalir.fr>
802
803 Web: http://dleone.fensalir.fr/
804 GPG: 0x82EB4DDF
805
806 From sascha-ml-reply-to-2011-2@silbe.org Sun Mar 13 16:21:06 2011
807 From: sascha-ml-reply-to-2011-2@silbe.org (Sascha Silbe)
808 Date: Sun, 13 Mar 2011 21:21:06 +0100
809 Subject: [sup-devel] [PATCHES] Add an account selector in edit-mode
810 In-Reply-To: <1300032642-sup-9716@mailer>
811 References: <1300032642-sup-9716@mailer>
812 Message-ID: <1300045320-sup-8627@twin.sascha.silbe.org>
813
814 Excerpts from Damien Leone's message of Sun Mar 13 17:13:05 +0100 2011:
815
816 > Sup guys,
817 >
818 > Please see commit messages for detailed informations.
819
820 > Attachment: 0001-reply-mode-improve-the-way-headers-are-handled.patch
821
822 This one would possibly break my workflow. My From address is chosen in
823 the before-edit hook based on the set of recipients. Since you only
824 call before-edit once with headers_full as headers, whatever From
825 address gets chosen for the initial reply mode will "stick".
826
827 It also seems that something I wanted to do for some time was already
828 possible with the old code, but isn't anymore with yours: Changing the
829 contents of the To and CC fields for the selector. Even arbitrary headers
830 (Mail-Followup-To in my case) could be keyed on the selector. I now
831 understand why before-edit was invoked multiple times. :)
832
833 And the part where I need to avoid modifying the body on subsequent
834 invocations looks like a bug in the original code: @bodies[k] should
835 contain a _copy_ of body (currently all @bodies[k] contain a reference
836 to the same instance, rendering the Hash useless).
837
838 BTW, do you know about Hash.merge! ? Some parts of your code could have
839 been simplified by using merge! instead of merge.
840
841 Sascha
842
843 --
844 http://sascha.silbe.org/
845 http://www.infra-silbe.de/
846 -------------- next part --------------
847 A non-text attachment was scrubbed...
848 Name: signature.asc
849 Type: application/pgp-signature
850 Size: 500 bytes
851 Desc: not available
852 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20110313/9b0ba930/attachment.bin>
853
854 From snaipperi@gmail.com Mon Mar 21 14:38:31 2011
855 From: snaipperi@gmail.com (Matti Eiden)
856 Date: Mon, 21 Mar 2011 20:38:31 +0200
857 Subject: [sup-devel] Ruby 1.9.2 Rakefile & LOAD_PATH
858 Message-ID: <AANLkTim7rVtS4+b-Pbv-DLNKYh-bSCjnUT=thDAJJmZM@mail.gmail.com>
859
860 Hey folks,
861
862 I posted on sup-talk in last December about an issue in the Rakefile
863 of sup when it comes to Ruby 1.9.2. The whole thing boils down to
864 this: https://rails.lighthouseapp.com/projects/8994/tickets/2921
865
866 Ruby 1.9.2 doesn't include the "." into LOAD_PATH anymore. Would
867 anybody like to fix this in the master? The fix is simple, just adding
868 "./" in front of the paths of the sup-version.rb and sup-files.rb. I
869 don't see why this would affect earlier Ruby versions in a negative
870 way, but of course I recommend testing it works before commiting to
871 the git.
872
873 Made merge request @ http://gitorious.org/sup/mainline/merge_requests/11
874
875 Patch also below.
876
877 Regards,
878 Matti Eiden
879
880
881
882 diff -aur sup-build/Rakefile sup-build.new/Rakefile
883 --- sup-build/Rakefile 2011-03-21 19:44:57.000000000 +0200
884 +++ sup-build.new/Rakefile 2011-03-21 19:52:37.000000000 +0200
885 @@ -31,8 +31,8 @@
886
887 $:.push "lib"
888 require 'rubygems'
889 -require "sup-files"
890 -require "sup-version"
891 +require "./sup-files"
892 +require "./sup-version"
893 require 'rake/gempackagetask.rb'
894
895 spec = Gem::Specification.new do |s|
896
897 From eg@gaute.vetsj.com Mon Mar 21 20:11:16 2011
898 From: eg@gaute.vetsj.com (Gaute Hope)
899 Date: Tue, 22 Mar 2011 01:11:16 +0100
900 Subject: [sup-devel] [issue132] strange encoding error
901 In-Reply-To: <1290508608.33.0.253409523291.issue132@masanjin.net>
902 References: <1290508608.33.0.253409523291.issue132@masanjin.net>
903 Message-ID: <1300752553-sup-725@qwerzila>
904
905 Excerpts from anonymous's message of 2010-11-23 11:36:48 +0100:
906 >
907 > New submission from anonymous:
908 >
909 > this happens when i try to send an email...
910 >
911 > ----------------------------------------------------------------
912 > --- Encoding::CompatibilityError from thread: main
913 > incompatible character encodings: UTF-8 and ASCII-8BIT
914 > /usr/lib/ruby/gems/1.9.1/gems/rmail-1.0.0/lib/rmail/serialize.rb:112:in
915 > `serialize_low'
916 > /usr/lib/ruby/gems/1.9.1/gems/rmail-1.0.0/lib/rmail/serialize.rb:99:in `block in
917
918 Hi,
919
920 ran into the same problem today; this seems to be a problem with rmail.
921 Apply this patch to the installed gem:
922
923
924 diff -ru rmail-1.0.0/lib/rmail/serialize.rb rmail-1.0.0-new//lib/rmail/serialize.rb
925 --- rmail-1.0.0/lib/rmail/serialize.rb 2011-03-22 01:08:07.413333337 +0100
926 +++ rmail-1.0.0-new//lib/rmail/serialize.rb 2011-03-22 01:07:45.183333337 +0100
927 @@ -109,6 +109,7 @@
928 @output << message.header.to_s
929 unless message.body.nil?
930 @output << "\n"
931 + message.body.force_encoding 'UTF-8'
932 @output << message.body
933 if depth == 0 and message.body.length > 0 and
934 message.body[-1] != ?\n
935
936 Best regards,
937 Gaute Hope
938
939 From wmorgan-sup@masanjin.net Sun Mar 27 16:41:59 2011
940 From: wmorgan-sup@masanjin.net (William Morgan)
941 Date: Sun, 27 Mar 2011 20:41:59 +0000
942 Subject: [sup-devel] sup v2 progress report
943 Message-ID: <1301257195-sup-9486@masanjin.net>
944
945 Hello all,
946
947 I'm happy to report that Sup version 2 is well underway!
948
949 Sup version 2 features:
950 - a client/server model that works over HTTP, allowing
951 a) development of other clients, e.g. web-based and phone-based
952 b) simultaneous access from multiple clients
953 c) IMAP emulation, aka no more lock-in!
954 - an improved console-based client
955
956 Heliotrope, the server component, is close to ready for a version 1 release.
957 You can find it at https://github.com/wmorgan/heliotrope/.
958
959 The client, which I'm calling Turnsole, is coming along swimmingly. I hope to
960 release a pre-alpha some-stuff-actually-works version within the next few days.
961 Much of the UI code has been borrowed from Sup, but the internals are quite
962 different:
963 - it's event-based, rather than thread-based, which streamlines a lot of the
964 code and avoids a whole big class of bugs.
965 - all the index and email threading code is ripped out
966 - most of the email parsing code is gone
967 - it handles Ruby 1.9 string encoding stuff correctly, rather than having
968 random checks scattered around
969
970 I think you're going to like it, since:
971 - the threads are pre-computed on the server side, so it's much, much faster
972 - you can finally view attachments locally!
973
974 Stay tuned for more. We're still a ways off before it's a drop-in replacement,
975 but I'm excited about how everything is coming together.
976 --
977 William <wmorgan-sup at masanjin.net>
978
979 From nicolas.pouillard@gmail.com Mon Mar 28 08:52:52 2011
980 From: nicolas.pouillard@gmail.com (Nicolas Pouillard)
981 Date: Mon, 28 Mar 2011 05:52:52 -0700 (PDT)
982 Subject: [sup-devel] sup v2 progress report
983 In-Reply-To: <1301257195-sup-9486@masanjin.net>
984 References: <1301257195-sup-9486@masanjin.net>
985 Message-ID: <4d9084a4.cc7e0e0a.6404.ffff8fad@mx.google.com>
986
987 On Sun, 27 Mar 2011 20:41:59 +0000, William Morgan <wmorgan-sup at masanjin.net> wrote:
988 > Hello all,
989 >
990 > I'm happy to report that Sup version 2 is well underway!
991 >
992 > Sup version 2 features:
993 > - a client/server model that works over HTTP, allowing
994 > a) development of other clients, e.g. web-based and phone-based
995 > b) simultaneous access from multiple clients
996 > c) IMAP emulation, aka no more lock-in!
997 > - an improved console-based client
998 >
999 > Heliotrope, the server component, is close to ready for a version 1 release.
1000 > You can find it at https://github.com/wmorgan/heliotrope/.
1001 >
1002 > The client, which I'm calling Turnsole, is coming along swimmingly. I hope to
1003 > release a pre-alpha some-stuff-actually-works version within the next few days.
1004 > Much of the UI code has been borrowed from Sup, but the internals are quite
1005 > different:
1006 > - it's event-based, rather than thread-based, which streamlines a lot of the
1007 > code and avoids a whole big class of bugs.
1008 > - all the index and email threading code is ripped out
1009 > - most of the email parsing code is gone
1010 > - it handles Ruby 1.9 string encoding stuff correctly, rather than having
1011 > random checks scattered around
1012 >
1013 > I think you're going to like it, since:
1014 > - the threads are pre-computed on the server side, so it's much, much faster
1015 > - you can finally view attachments locally!
1016 >
1017 > Stay tuned for more. We're still a ways off before it's a drop-in replacement,
1018 > but I'm excited about how everything is coming together.
1019
1020 While mass importing an mbox I got this:
1021
1022 $ ... heliotrope-add ...
1023 ; forced to decode html. running html2text on 868b mime part...
1024 end offset is 237534473
1025 .../heliotrope/lib/heliotrope/decoder.rb:109:in `gsub': incompatible character encodings: UTF-8 and ASCII-8BIT (Encoding::CompatibilityError)
1026 from .../heliotrope/lib/heliotrope/decoder.rb:109:in `decode_rfc2047'
1027 from .../heliotrope/lib/heliotrope/message.rb:208:in `decode_header'
1028 from .../heliotrope/lib/heliotrope/message.rb:30:in `parse!'
1029 from bin/heliotrope-add:105:in `<main>'
1030
1031 Best regards,
1032
1033 --
1034 Nicolas Pouillard
1035 http://nicolaspouillard.fr
1036
1037 From wmorgan-sup@masanjin.net Mon Mar 28 18:57:26 2011
1038 From: wmorgan-sup@masanjin.net (William Morgan)
1039 Date: Mon, 28 Mar 2011 22:57:26 +0000
1040 Subject: [sup-devel] [sup-talk] sup v2 progress report
1041 In-Reply-To: <AANLkTimqLoHDVWNpwUsFAc+E9csfxgwUwCWsuo08a5QJ@mail.gmail.com>
1042 References: <1301257195-sup-9486@masanjin.net>
1043 <AANLkTimqLoHDVWNpwUsFAc+E9csfxgwUwCWsuo08a5QJ@mail.gmail.com>
1044 Message-ID: <1301353031-sup-7684@masanjin.net>
1045
1046 Reformatted excerpts from Matthieu Rakotojaona's message of 2011-03-28:
1047 > I have tried the new system a little bit, and I have a few things to say :
1048 > - you must have 'html2text' (not specified) installed on your system,
1049 > as long as you have any html mail. I think this is the case for too
1050 > many of us, unfortunately.
1051 > - I didn't find rubymail with gem, but found it under the name rmail
1052
1053 Thanks, I will update the README.
1054
1055 > - I still had some problem with the encoding stuff. I was using ruby
1056 > v1.9.2 (or so I thought), but got the "ArgumentError - invalid byte
1057 > sequence in UTF-8" error.
1058
1059 Ok, I'm still working on tracking this down. If you have a backtrace
1060 handy, that would be useful.
1061
1062 > - Is sup development bound to be stopped, at least when
1063 > heliotrope/turnsole will be ready ?
1064
1065 I'm planning on moving my efforts entirely over to heliotrope +
1066 turnsole. Which isn't that big of a deal, really, since I haven't done
1067 much on Sup for years.
1068
1069 > - Is there any mailing-list for this new project, or should we keep
1070 > using those related with sup ?
1071
1072 I'll keep talking about it here until people complain.
1073
1074 > - Do you have any address where I can find and test turnsole ?
1075
1076 Check back in a few days.
1077 --
1078 William <wmorgan-sup at masanjin.net>
1079
1080 From wmorgan-sup@masanjin.net Mon Mar 28 23:11:04 2011
1081 From: wmorgan-sup@masanjin.net (William Morgan)
1082 Date: Tue, 29 Mar 2011 03:11:04 +0000
1083 Subject: [sup-devel] sup v2 progress report
1084 In-Reply-To: <4d9084a4.cc7e0e0a.6404.ffff8fad@mx.google.com>
1085 References: <1301257195-sup-9486@masanjin.net>
1086 <4d9084a4.cc7e0e0a.6404.ffff8fad@mx.google.com>
1087 Message-ID: <1301368236-sup-9189@masanjin.net>
1088
1089 Reformatted excerpts from Nicolas Pouillard's message of 2011-03-28:
1090 > .../heliotrope/lib/heliotrope/decoder.rb:109:in `gsub': incompatible character encodings: UTF-8 and ASCII-8BIT (Encoding::CompatibilityError)
1091
1092 Hm. I think I know what the problem is. Stay tuned.
1093 --
1094 William <wmorgan-sup at masanjin.net>
1095
1096 From wmorgan-sup@masanjin.net Tue Mar 29 00:00:36 2011
1097 From: wmorgan-sup@masanjin.net (William Morgan)
1098 Date: Tue, 29 Mar 2011 04:00:36 +0000
1099 Subject: [sup-devel] sup v2 progress report
1100 In-Reply-To: <4d9084a4.cc7e0e0a.6404.ffff8fad@mx.google.com>
1101 References: <1301257195-sup-9486@masanjin.net>
1102 <4d9084a4.cc7e0e0a.6404.ffff8fad@mx.google.com>
1103 Message-ID: <1301371130-sup-6618@masanjin.net>
1104
1105 Reformatted excerpts from Nicolas Pouillard's message of 2011-03-28:
1106 > .../heliotrope/lib/heliotrope/decoder.rb:109:in `gsub': incompatible
1107 > character encodings: UTF-8 and ASCII-8BIT
1108 > (Encoding::CompatibilityError)
1109
1110 Can you try with the latest master? If it still doesn't work, are you
1111 able to narrow down the string encodings of from and word?
1112
1113 This 1.9 string encoding stuff is tricky business, especially combined
1114 with the messy world of email. I think I'm getting close.
1115 --
1116 William <wmorgan-sup at masanjin.net>
1117
1118 From nicolas.pouillard@gmail.com Tue Mar 29 17:19:00 2011
1119 From: nicolas.pouillard@gmail.com (Nicolas Pouillard)
1120 Date: Tue, 29 Mar 2011 14:19:00 -0700 (PDT)
1121 Subject: [sup-devel] sup v2 progress report
1122 In-Reply-To: <1301371130-sup-6618@masanjin.net>
1123 References: <1301257195-sup-9486@masanjin.net>
1124 <4d9084a4.cc7e0e0a.6404.ffff8fad@mx.google.com>
1125 <1301371130-sup-6618@masanjin.net>
1126 Message-ID: <4d924cc4.5925e30a.5311.ffffc603@mx.google.com>
1127
1128 On Tue, 29 Mar 2011 04:00:36 +0000, William Morgan <wmorgan-sup at masanjin.net> wrote:
1129 > Reformatted excerpts from Nicolas Pouillard's message of 2011-03-28:
1130 > > .../heliotrope/lib/heliotrope/decoder.rb:109:in `gsub': incompatible
1131 > > character encodings: UTF-8 and ASCII-8BIT
1132 > > (Encoding::CompatibilityError)
1133 >
1134 > Can you try with the latest master? If it still doesn't work, are you
1135 > able to narrow down the string encodings of from and word?
1136 >
1137 > This 1.9 string encoding stuff is tricky business, especially combined
1138 > with the messy world of email. I think I'm getting close.
1139
1140 Nice, it seems to go a lot further. However there seems to be some strange
1141 blocking behavior, like using CPU and producing nothing in hours.
1142
1143 --
1144 Nicolas Pouillard
1145 http://nicolaspouillard.fr
1146
1147 From wmorgan-sup@masanjin.net Tue Mar 29 17:31:06 2011
1148 From: wmorgan-sup@masanjin.net (William Morgan)
1149 Date: Tue, 29 Mar 2011 21:31:06 +0000
1150 Subject: [sup-devel] sup v2 progress report
1151 In-Reply-To: <4d924cc4.5925e30a.5311.ffffc603@mx.google.com>
1152 References: <1301257195-sup-9486@masanjin.net>
1153 <4d9084a4.cc7e0e0a.6404.ffff8fad@mx.google.com>
1154 <1301371130-sup-6618@masanjin.net>
1155 <4d924cc4.5925e30a.5311.ffffc603@mx.google.com>
1156 Message-ID: <1301434157-sup-5884@masanjin.net>
1157
1158 Reformatted excerpts from Nicolas Pouillard's message of 2011-03-29:
1159 > Nice, it seems to go a lot further. However there seems to be some strange
1160 > blocking behavior, like using CPU and producing nothing in hours.
1161
1162 Weird. I wonder if it's triggering some regex worst case like we've seen
1163 before in Sup. Are you able to narrow down what message or text is
1164 causing this? I will add a --verbose option, which might make this
1165 easier.
1166 --
1167 William <wmorgan-sup at masanjin.net>
1168
1169 From matthieu.rakotojaona@gmail.com Mon Mar 28 00:14:24 2011
1170 From: matthieu.rakotojaona@gmail.com (Matthieu Rakotojaona)
1171 Date: Mon, 28 Mar 2011 06:14:24 +0200
1172 Subject: [sup-devel] [sup-talk] sup v2 progress report
1173 In-Reply-To: <1301257195-sup-9486@masanjin.net>
1174 References: <1301257195-sup-9486@masanjin.net>
1175 Message-ID: <AANLkTimqLoHDVWNpwUsFAc+E9csfxgwUwCWsuo08a5QJ@mail.gmail.com>
1176
1177 Thank you very much.
1178
1179 I've been using sup for quite a few months now, and I must say that
1180 the labels-centric point of view really is an improvement over the
1181 other mail management systems.
1182 I've been following sup news very closely, and I'm really excited
1183 about heliotrope/turnsole.
1184
1185 I have tried the new system a little bit, and I have a few things to say :
1186 - you must have 'html2text' (not specified) installed on your system,
1187 as long as you have any html mail. I think this is the case for too
1188 many of us, unfortunately.
1189 - I didn't find rubymail with gem, but found it under the name rmail
1190 - I still had some problem with the encoding stuff. I was using ruby
1191 v1.9.2 (or so I thought), but got the "ArgumentError - invalid byte
1192 sequence in UTF-8" error. Strange thing, the log showed me evidence
1193 that I was using ruby v1.9.1 (problems came from files in
1194 "/usr/lib/ruby/gems/1.9.1"). So I switched back to v1.8.7 from AUR
1195 (I'm using archlinux), and the problem just went away.
1196
1197 In the light of what you wrote, I have two questions :
1198 - Is sup development bound to be stopped, at least when
1199 heliotrope/turnsole will be ready ?
1200 - Is there any mailing-list for this new project, or should we keep
1201 using those related with sup ?
1202 - Do you have any address where I can find and test turnsole ?
1203
1204 Again, thank you very much for your work and your help, and I'm
1205 talking to everyone on these lists.
1206
1207 Regards,
1208
1209 --
1210 Matthieu RAKOTOJAONA
1211