community/pipermail-archives/sup-talk/2007-07.txt (57557B) - raw
1 From wmorgan-sup@masanjin.net Tue Jul 3 17:45:04 2007
2 From: wmorgan-sup@masanjin.net (William Morgan)
3 Date: Tue, 03 Jul 2007 14:45:04 -0700
4 Subject: [sup-talk] new in svn: per-account signatures
5 In-Reply-To: <1181779547-sup-1059@mona>
6 References: <1181696943-sup-559@south> <1181779547-sup-1059@mona>
7 Message-ID: <1183499104-sup-9767@south>
8
9 Excerpts from jeff.covey's message of Wed Jun 13 17:10:11 -0700 2007:
10 > this seems to work well. unfortunately, i like having the signature block
11 > passed to the editor. :)
12
13 In SVN trunk now, if you specify :edit_signatures: true, you'll always
14 get the default account's signature, and it will be passed to the
15 editor. The default is false.
16
17 --
18 William <wmorgan-sup at masanjin.net>
19
20 From wmorgan-sup@masanjin.net Tue Jul 3 18:08:04 2007
21 From: wmorgan-sup@masanjin.net (William Morgan)
22 Date: Tue, 03 Jul 2007 15:08:04 -0700
23 Subject: [sup-talk] mutt's auto_view and alternative_order
24 In-Reply-To: <1181834033-sup-8054@mona>
25 References: <1181834033-sup-8054@mona>
26 Message-ID: <1183500484-sup-7622@south>
27
28 Excerpts from jeff.covey's message of Thu Jun 14 08:32:09 -0700 2007:
29 > something i'm really missing from mutt is the auto_view setting for mime
30 > types.
31 [snip]
32 > it would be great if config.yaml let the user specify a list of mime types
33 > which should have their attachments run through the .mailcap-specified
34 > filters with copiousoutput tags, and have the results inserted into the text
35 > of the message. i think it might be good to keep the "mime attachment" line
36 > as well, so that hitting enter on it would launch an external viewer for the
37 > times you want that.
38
39 Yup, I agree that this is a highly desirable thing. I'm going to try and
40 handle as much of this type of thing as possible through the
41 aforementioned hook system. It definitely won't happen for the next
42 release, though.
43
44 --
45 William <wmorgan-sup at masanjin.net>
46
47 From jeff.covey@pobox.com Tue Jul 3 21:13:29 2007
48 From: jeff.covey@pobox.com (jeff covey)
49 Date: Tue, 03 Jul 2007 21:13:29 -0400
50 Subject: [sup-talk] new in svn: per-account signatures
51 In-Reply-To: <1183499104-sup-9767@south>
52 References: <1181696943-sup-559@south> <1181779547-sup-1059@mona>
53 <1183499104-sup-9767@south>
54 Message-ID: <1183511439-sup-3890@mona>
55
56 Excerpts from William Morgan's message of Tue Jul 03 17:45:04 -0400 2007:
57
58 > In SVN trunk now, if you specify :edit_signatures: true, you'll always get
59 > the default account's signature, and it will be passed to the editor.
60
61 you seem to have meant ":edit_signature:" (singular), as it's working with
62 that (and sup+ferret are behaving again, so i'm a supper again for as long
63 as it holds). thanks!
64
65 --
66 jeff covey
67 http://jeffcovey.net/
68
69
70 From wmorgan-sup@masanjin.net Tue Jul 3 22:42:56 2007
71 From: wmorgan-sup@masanjin.net (William Morgan)
72 Date: Tue, 03 Jul 2007 19:42:56 -0700
73 Subject: [sup-talk] new in svn: per-account signatures
74 In-Reply-To: <1183511439-sup-3890@mona>
75 References: <1181696943-sup-559@south> <1181779547-sup-1059@mona>
76 <1183499104-sup-9767@south> <1183511439-sup-3890@mona>
77 Message-ID: <1183516855-sup-2983@south>
78
79 Excerpts from jeff.covey's message of Tue Jul 03 18:13:29 -0700 2007:
80 > you seem to have meant ":edit_signature:" (singular), as it's working
81 > with that
82
83 Oops, yes.
84
85 > (and sup+ferret are behaving again, so i'm a supper again for as long
86 > as it holds). thanks!
87
88 Great, but it definitely won't last. So keep backing up. :)
89
90 I've posted to ferret-talk in the meanwhile. I'll let you know what
91 comes of it. If it happens again, keep a copy of the index, because a
92 postmortem might be necessary.
93
94 --
95 William <wmorgan-sup at masanjin.net>
96
97 From wmorgan-sup@masanjin.net Tue Jul 3 22:55:56 2007
98 From: wmorgan-sup@masanjin.net (William Morgan)
99 Date: Tue, 03 Jul 2007 19:55:56 -0700
100 Subject: [sup-talk] GPG Support
101 In-Reply-To: <1182210252-sup-8502@mona>
102 References: <D55C81AD71647428E7B489B6@Sumatra.local> <1182210252-sup-8502@mona>
103 Message-ID: <1183517242-sup-3554@south>
104
105 Excerpts from jeff.covey's message of Mon Jun 18 17:00:52 -0700 2007:
106 > Excerpts from Chris Lee's message of Thu May 17 17:24:11 -0400 2007:
107 > > The sources.yaml file is pgp encrypted now.
108 >
109 > why is that? there doesn't seem to be any sensitive information in
110 > sources.yaml, and encrypting it makes it harder to deal with.
111
112 For IMAP and mbox+ssh sources, the username and password is stored in
113 sources.yaml. Sup is careful to create it with the right unix mode, so
114 I'm not convinced of the vital necessity of this feature, but I'm not
115 opposed to its very existence either.
116
117 > i wouldn't bother with storing passwords/phrases and encrypting files,
118 > i would just let gpg prompt people for the words/phrases as needed.
119 > if they don't want to type them each time, they can use something like
120 > gpg-agent.
121
122 I tend to agree. I'm happy to offload as much functionality to other
123 programs as possible.
124
125 > i only use one key myself, but it would be nice to be able to specify a key
126 > for each account under ":accounts:".
127
128 Agreed.
129
130 I haven't incorporated Chris's patch yet, mostly because I wanted to
131 flesh out Sup's multi-account support, but now that things are better on
132 that end, I do plan to revisit the issue. Chris, if you're still there,
133 please don't feel like I've ignored you.
134
135 --
136 William <wmorgan-sup at masanjin.net>
137
138 From jeff.covey@pobox.com Wed Jul 4 10:07:55 2007
139 From: jeff.covey@pobox.com (jeff covey)
140 Date: Wed, 04 Jul 2007 10:07:55 -0400
141 Subject: [sup-talk] new in svn: per-account signatures
142 In-Reply-To: <1183516855-sup-2983@south>
143 References: <1181696943-sup-559@south> <1181779547-sup-1059@mona>
144 <1183499104-sup-9767@south> <1183511439-sup-3890@mona>
145 <1183516855-sup-2983@south>
146 Message-ID: <1183558009-sup-2970@mona>
147
148 Excerpts from William Morgan's message of Tue Jul 03 22:42:56 -0400 2007:
149
150 > it definitely won't last. So keep backing up. :)
151
152 in the meantime, i'm getting to remember how much faster i can process my
153 mail with sup. :)
154
155 thanks,
156
157 --
158 jeff covey
159 http://jeffcovey.net/
160
161
162 From wmorgan-sup@masanjin.net Fri Jul 6 14:55:49 2007
163 From: wmorgan-sup@masanjin.net (William Morgan)
164 Date: Fri, 06 Jul 2007 11:55:49 -0700
165 Subject: [sup-talk] new in svn: attachments!
166 Message-ID: <1183748022-sup-9835@south>
167
168 In addition to slightly better MIME support, you can now add attachments
169
170 to messages! Still TBD: save attachment selection when postponing;
171
172 better error-handling, and multi-selection.
173
174
175
176 Try it out and let me know what you think. Now that tab completion
177
178 is enabled, I'm going to tweak a couple other things in the UI as well.
179
180 --
181 William <wmorgan-sup at masanjin.net>
182
183 From itaylor@uark.edu Fri Jul 6 16:20:47 2007
184 From: itaylor@uark.edu (Ian Taylor)
185 Date: Fri, 06 Jul 2007 15:20:47 -0500
186 Subject: [sup-talk] new in svn: attachments!
187 In-Reply-To: <1183748022-sup-9835@south>
188 References: <1183748022-sup-9835@south>
189 Message-ID: <1183753190-sup-5411@zap>
190
191 Excerpts from William Morgan's message of Fri Jul 06 13:55:49 -0500 2007:
192
193 > In addition to slightly better MIME support, you can now add attachments
194
195 >
196
197 > to messages! Still TBD: save attachment selection when postponing;
198
199 >
200
201 > better error-handling, and multi-selection.
202
203 >
204
205 >
206
207 >
208
209 > Try it out and let me know what you think. Now that tab completion
210
211 >
212
213 > is enabled, I'm going to tweak a couple other things in the UI as well.
214
215 >
216
217
218
219 I just sent a message with an attachment. When viewing that same
220
221 message marked as +sent, the attachment doesn't show up.
222
223 --
224 Ian Taylor, Technical Assistant
225 Computer Science Computer Engineering
226 http://www.csce.uark.edu itaylor at uark.edu
227 University of Arkansas
228
229
230 From wmorgan-sup@masanjin.net Fri Jul 6 17:48:06 2007
231 From: wmorgan-sup@masanjin.net (William Morgan)
232 Date: Fri, 06 Jul 2007 14:48:06 -0700
233 Subject: [sup-talk] new in svn: attachments!
234 In-Reply-To: <1183753190-sup-5411@zap>
235 References: <1183748022-sup-9835@south> <1183753190-sup-5411@zap>
236 Message-ID: <1183758460-sup-6685@south>
237
238 Excerpts from Ian Taylor's message of Fri Jul 06 13:20:47 -0700 2007:
239
240 > I just sent a message with an attachment. When viewing that same
241
242 > message marked as +sent, the attachment doesn't show up.
243
244
245
246 Fixed!
247
248 --
249 William <wmorgan-sup at masanjin.net>
250
251 From jeff.covey@pobox.com Fri Jul 6 18:16:30 2007
252 From: jeff.covey@pobox.com (jeff covey)
253 Date: Fri, 06 Jul 2007 18:16:30 -0400
254 Subject: [sup-talk] new in svn: attachments!
255 In-Reply-To: <1183748022-sup-9835@south>
256 References: <1183748022-sup-9835@south>
257 Message-ID: <1183760137-sup-7750@mona>
258
259 lest anyone have the same trouble:
260
261
262
263 you need to "gem install mime-types" for this svn update.
264
265
266
267 thanks,
268
269
270
271 --
272
273 jeff covey
274
275 http://jeffcovey.net/
276
277
278
279 From wmorgan-sup@masanjin.net Sat Jul 7 09:17:23 2007
280 From: wmorgan-sup@masanjin.net (William Morgan)
281 Date: Sat, 07 Jul 2007 06:17:23 -0700
282 Subject: [sup-talk] sup dying with another ferret error
283 In-Reply-To: <20070630092906.GA16008@mona.jeffcovey.net>
284 References: <20070630092906.GA16008@mona.jeffcovey.net>
285 Message-ID: <1183814217-sup-1488@south>
286
287 Excerpts from jeff.covey's message of Sat Jun 30 02:29:07 -0700 2007:
288
289 > The problem was: 'IO Error occured at <except.c>:93 in xraise
290
291 > Error occured in index.c:901 - sis_find_segments_file
292
293
294
295 Do you have a really large index? Like, 4G?
296
297 --
298 William <wmorgan-sup at masanjin.net>
299
300 From jeff.covey@pobox.com Sat Jul 7 08:17:14 2007
301 From: jeff.covey@pobox.com (jeff covey)
302 Date: Sat, 07 Jul 2007 08:17:14 -0400
303 Subject: [sup-talk] sup failing to display the text of a message
304 In-Reply-To: <20070611013051.GA12580@mona.jeffcovey.net>
305 References: <20070611013051.GA12580@mona.jeffcovey.net>
306 Message-ID: <1183810570-sup-4651@mona>
307
308 Excerpts from jeff covey's message of Sun Jun 10 21:30:51 -0400 2007:
309
310
311
312 > sup's displaying the attached message as though it has no text at all; it
313
314 > doesn't even show the two sections as attachments that can be viewed.
315
316
317
318 with the new mime code, this is now showing as:
319
320
321
322 x Attachment: sup-attachment-1183810370-1070 (multipart/mixed)
323
324
325
326 thanks!
327
328
329
330 --
331
332 jeff covey
333
334 http://jeffcovey.net/
335
336
337
338 From jeff.covey@pobox.com Sat Jul 7 22:32:10 2007
339 From: jeff.covey@pobox.com (jeff covey)
340 Date: Sat, 07 Jul 2007 22:32:10 -0400
341 Subject: [sup-talk] sup dying with another ferret error
342 In-Reply-To: <1183814217-sup-1488@south>
343 References: <20070630092906.GA16008@mona.jeffcovey.net>
344 <1183814217-sup-1488@south>
345 Message-ID: <1183861808-sup-44@mona>
346
347 Excerpts from William Morgan's message of Sat Jul 07 09:17:23 -0400 2007:
348
349
350
351 > Do you have a really large index? Like, 4G?
352
353
354
355 no, not very big:
356
357
358
359 $ du -hs ~/.sup/ferret/
360
361 14M /home/jeff/.sup/ferret/
362
363
364
365 thanks,
366
367
368
369 --
370
371 jeff covey
372
373 http://jeffcovey.net/
374
375
376
377 From jeff.covey@pobox.com Sat Jul 7 22:59:59 2007
378 From: jeff.covey@pobox.com (jeff covey)
379 Date: Sat, 07 Jul 2007 22:59:59 -0400
380 Subject: [sup-talk] extra blank lines
381 In-Reply-To: <1183861808-sup-44@mona>
382 References: <20070630092906.GA16008@mona.jeffcovey.net>
383 <1183814217-sup-1488@south> <1183861808-sup-44@mona>
384 Message-ID: <1183863440-sup-3959@mona>
385
386 all of the messages i've sent with sup since the latest svn updates seem to
387
388 be including a lot of extra blank lines. for example:
389
390
391
392 Excerpts from jeff covey's message of Sat Jul 07 22:32:10 -0400 2007:
393
394 > Excerpts from William Morgan's message of Sat Jul 07 09:17:23 -0400 2007:
395
396 >
397
398 > > Do you have a really large index? Like, 4G?
399
400 >
401
402 >
403
404 >
405
406 > no, not very big:
407
408 >
409
410 >
411
412 >
413
414 > $ du -hs ~/.sup/ferret/
415
416 >
417
418 > 14M /home/jeff/.sup/ferret/
419
420 >
421
422 >
423
424 >
425
426 > thanks,
427
428 >
429
430
431
432 --
433
434 jeff covey
435
436 http://jeffcovey.net/
437
438
439
440 From wmorgan-sup@masanjin.net Sun Jul 8 11:14:45 2007
441 From: wmorgan-sup@masanjin.net (William Morgan)
442 Date: Sun, 08 Jul 2007 08:14:45 -0700
443 Subject: [sup-talk] extra blank lines
444 In-Reply-To: <1183863440-sup-3959@mona>
445 References: <20070630092906.GA16008@mona.jeffcovey.net>
446 <1183814217-sup-1488@south> <1183861808-sup-44@mona>
447 <1183863440-sup-3959@mona>
448 Message-ID: <1183907631-sup-1423@south>
449
450 Excerpts from jeff.covey's message of Sat Jul 07 19:59:59 -0700 2007:
451 > all of the messages i've sent with sup since the latest svn updates
452 > seem to be including a lot of extra blank lines.
453
454 If these two lines are together,
455 this problem should be fixed.
456
457 --
458 William <wmorgan-sup at masanjin.net>
459
460 From wmorgan-sup@masanjin.net Sun Jul 8 11:44:22 2007
461 From: wmorgan-sup@masanjin.net (William Morgan)
462 Date: Sun, 08 Jul 2007 08:44:22 -0700
463 Subject: [sup-talk] sup failing to display the text of a message
464 In-Reply-To: <1183810570-sup-4651@mona>
465 References: <20070611013051.GA12580@mona.jeffcovey.net>
466 <1183810570-sup-4651@mona>
467 Message-ID: <1183908397-sup-1704@south>
468
469 Excerpts from jeff.covey's message of Sat Jul 07 05:17:14 -0700 2007:
470 > with the new mime code, this is now showing as:
471 > x Attachment: sup-attachment-1183810370-1070 (multipart/mixed)
472
473 Hm, that's still not quite what I want, though. What should happen with
474 is that multipart thing shouldn't be displayed at all, and instead you
475 should see two inlined, collapsable, individually-savable attachments.
476
477 I've committed a change that should have this behavior. But I couldn't
478 replicate your version from the original message, which is curious, so
479 let me know how it looks.
480
481 --
482 William <wmorgan-sup at masanjin.net>
483
484 From jeff.covey@pobox.com Sun Jul 8 14:59:51 2007
485 From: jeff.covey@pobox.com (jeff covey)
486 Date: Sun, 08 Jul 2007 14:59:51 -0400
487 Subject: [sup-talk] extra blank lines
488 In-Reply-To: <1183907631-sup-1423@south>
489 References: <20070630092906.GA16008@mona.jeffcovey.net>
490 <1183814217-sup-1488@south> <1183861808-sup-44@mona>
491 <1183863440-sup-3959@mona> <1183907631-sup-1423@south>
492 Message-ID: <1183921167-sup-6729@mona>
493
494 Excerpts from William Morgan's message of Sun Jul 08 11:14:45 -0400 2007:
495
496 > If these two lines are together,
497 > this problem should be fixed.
498
499 looks good to me!
500
501 --
502 jeff covey
503 http://jeffcovey.net/
504
505
506 From jeff.covey@pobox.com Mon Jul 9 10:44:54 2007
507 From: jeff.covey@pobox.com (jeff covey)
508 Date: Mon, 09 Jul 2007 10:44:54 -0400
509 Subject: [sup-talk] sup failing to display the text of a message
510 In-Reply-To: <1183908397-sup-1704@south>
511 References: <20070611013051.GA12580@mona.jeffcovey.net>
512 <1183810570-sup-4651@mona> <1183908397-sup-1704@south>
513 Message-ID: <1183992180-sup-9883@mona>
514
515 Excerpts from William Morgan's message of Sun Jul 08 11:44:22 -0400 2007:
516
517 > What should happen with is that multipart thing shouldn't be displayed at
518 > all, and instead you should see two inlined, collapsable,
519 > individually-savable attachments. I've committed a change that should
520 > have this behavior.
521
522 it still looks the same to me:
523
524 http://jeffcovey.net/tmp/sup-fm_newsletter.png
525
526 thanks,
527
528 --
529 jeff covey
530 http://jeffcovey.net/
531
532
533 From wmorgan-sup@masanjin.net Tue Jul 10 11:45:38 2007
534 From: wmorgan-sup@masanjin.net (William Morgan)
535 Date: Tue, 10 Jul 2007 08:45:38 -0700
536 Subject: [sup-talk] sup failing to display the text of a message
537 In-Reply-To: <1183992180-sup-9883@mona>
538 References: <20070611013051.GA12580@mona.jeffcovey.net>
539 <1183810570-sup-4651@mona> <1183908397-sup-1704@south>
540 <1183992180-sup-9883@mona>
541 Message-ID: <1184081531-sup-3358@south>
542
543 Excerpts from jeff.covey's message of Mon Jul 09 07:44:54 -0700 2007:
544 > it still looks the same to me:
545 >
546 > http://jeffcovey.net/tmp/sup-fm_newsletter.png
547
548 Ok, I subscribed to fm-news just so I could figure out what was going on
549 here. The problem is that they don't send a MIME-Version: header in the
550 top-level message headers, so RubyMail doesn't interpret the email as a
551 MIME message. Which is correct, strictly speaking, though of course it's
552 better to follow the adage of "lenient in acceptance and strict in
553 emission". If you add a MIME-Version header back in, everything works as
554 it should.
555
556 To further confuse the issue, the version that you attached back at the
557 beginning of June apparently had its headers cleaned up by Mutt. Mutt
558 clearly has more lenient message parsing than RubyMail does, if it does
559 something reasonable with this message.
560
561 So I could patch RubyMail (which is completely unmaintained, so I'd
562 essentially have to publish the patch in parallel with Sup) to handle
563 these messages, which is dubious by the RFCs but probably fine in
564 practice, or I could just ignore the issue as "someone else's problem".
565 Since the message content is still viewable in Sup, I'm tempted to leave
566 things as is.
567
568 RubyMail really needs a maintainer.
569
570 --
571 William <wmorgan-sup at masanjin.net>
572
573 From jeff.covey@pobox.com Tue Jul 10 13:40:39 2007
574 From: jeff.covey@pobox.com (jeff covey)
575 Date: Tue, 10 Jul 2007 13:40:39 -0400
576 Subject: [sup-talk] sup failing to display the text of a message
577 In-Reply-To: <1184081531-sup-3358@south>
578 References: <20070611013051.GA12580@mona.jeffcovey.net>
579 <1183810570-sup-4651@mona> <1183908397-sup-1704@south>
580 <1183992180-sup-9883@mona> <1184081531-sup-3358@south>
581 Message-ID: <1184088645-sup-8679@mona>
582
583 Excerpts from William Morgan's message of Tue Jul 10 11:45:38 -0400 2007:
584
585 > So I could patch RubyMail (which is completely unmaintained, so I'd
586 > essentially have to publish the patch in parallel with Sup) to handle
587 > these messages, which is dubious by the RFCs but probably fine in
588 > practice, or I could just ignore the issue as "someone else's problem".
589 > Since the message content is still viewable in Sup, I'm tempted to leave
590 > things as is.
591
592 ok, thanks for checking into it!
593
594 --
595 jeff covey
596 http://jeffcovey.net/
597
598
599 From wmorgan-sup@masanjin.net Tue Jul 10 14:21:57 2007
600 From: wmorgan-sup@masanjin.net (William Morgan)
601 Date: Tue, 10 Jul 2007 11:21:57 -0700
602 Subject: [sup-talk] sup-sync-back not syncing all usual sources
603 In-Reply-To: <1182126871-sup-7739@mona>
604 References: <1181836972-sup-1140@mona> <1182112191-sup-9971@south>
605 <1182126871-sup-7739@mona>
606 Message-ID: <1184091559-sup-1633@south>
607
608 Excerpts from jeff.covey's message of Sun Jun 17 18:00:24 -0700 2007:
609 > thanks, it now spits out the names of all of my usual sources and
610 > moves deleted files from some, but not all of them.
611
612 This I'm still not sure about and I can't replicate. a) Does it still
613 happen with recent SVN, and b) are there any distinguishing features
614 about which sources it moves stuff from and which it wrongly ignores?
615
616 > would it make more sense for sup-sync-back to process only those
617 > sources which need to be synced back (at this stage in sup-sync-back's
618 > life, those which have spam/deleted messages)?
619
620 Great idea. This is in SVN now.
621
622 > also, at the end of running sup-sync-back without specifying a source, i get
623 > this:
624 >
625 > Scanning sup://sent...
626 > Scanned 4, deleted 0, moved 0 messages from sup://sent.
627 > [Sun Jun 17 20:32:34 -0400 2007] saving index and sources...
628 > [Sun Jun 17 20:32:35 -0400 2007] unlocking /home/jeff/.sup/lock...
629 > /usr/lib/ruby/1.8/fileutils.rb:505:in `rename': No such file or directory -
630 > /tmp/sup-sync-back-9998.1089.0 or (Errno::ENOENT)
631
632 This should be fixed as well.
633
634 Let me know how things are working for you.
635
636 --
637 William <wmorgan-sup at masanjin.net>
638
639 From jeff.covey@pobox.com Wed Jul 11 19:34:04 2007
640 From: jeff.covey@pobox.com (jeff covey)
641 Date: Wed, 11 Jul 2007 19:34:04 -0400
642 Subject: [sup-talk] sup concatenating many email addresses
643 Message-ID: <1184196401-sup-4306@mona>
644
645 some mail bounced, and when i went back to look in ~/.sup/sent.mbox, i found
646 messages with "to:" lines like this:
647
648 > From jeff.covey at pobox.com Sun Jul 08 17:14:45 -0400 2007
649 > Subject: opening the zendo on upcoming saturdays
650 > From: jeff covey <jeff.covey at pobox.com>
651 > To: mutei doug murphy <mutei at aol.com>nate butler <n8butler at yahoo.com>Jan & Michael Prenger <jmprenger1 at comcast.net>John and/or Martha Seay <mseay at comcast.net>erichj.kuhn <erichj.kuhn at gmail.com>Robert Williams <williams.rm at comcast.net>chunyuanlee <chunyuanlee at yahoo.com>
652 > Date: Sun, 08 Jul 2007 17:14:45 -0400
653 > Message-Id: <1183928946-sup-7677 at mona>
654 > User-Agent: Sup/0.0.8
655 > Content-Disposition: inline
656 > Content-Type: text/plain; charset=utf-8
657
658 this had looked just fine in the reply-mode buffer when i sent it, with each
659 email address on a separate line and a comma after each but the last.
660
661 the problem seems to be traced back to these lines in ~/.sup/people.txt:
662
663 mutei at aol.com: 1184195526 mutei doug murphy
664 chunyuanlee at yahoo.com: 1184195526 mutei doug murphy <mutei at aol.com>nate butler <n8butler at yahoo.com>Jan & Michael Prenger <jmprenger1 at comcast.net>John and/or Martha Seay <mseay at comcast.net>erichj.kuhn <erichj.kuhn at gmail.com>Robert Williams <williams.rm at comcast.net>chunyuanlee
665 mutei at aol.comn8butler@yahoo.comjmprenger1 at comcast.netmseay@comcast.neterichj.kuhn at gmail.comwilliams.rm@comcast.netchunyuanlee at yahoo.com: 1184195526 mutei
666 "mutei at aol.comn8butler@yahoo.comjmprenger1 at comcast.netmseay@comcast.neterichj.kuhn at gmail.comwilliams.rm@comcast.netchunyuanlee"@yahoo.com: 1184195679 mutei doug murphy nate butler Jan & Michael Prenger John and/or Martha Seay erichj.kuhn Robert Williams chunyuanlee
667
668 sup seems to be trying to do something clever but coming up with
669 progressively worse results. there are a couple of other lines in
670 people.txt which have oddly-run-together addresses, and i can't trust sup to
671 send email where it says it's sending it at the moment. :-\
672
673 thanks,
674
675 --
676 jeff covey
677 http://jeffcovey.net/
678
679
680 From wmorgan-sup@masanjin.net Thu Jul 12 11:39:21 2007
681 From: wmorgan-sup@masanjin.net (William Morgan)
682 Date: Thu, 12 Jul 2007 08:39:21 -0700
683 Subject: [sup-talk] sup concatenating many email addresses
684 In-Reply-To: <1184196401-sup-4306@mona>
685 References: <1184196401-sup-4306@mona>
686 Message-ID: <1184254483-sup-9640@south>
687
688 Excerpts from jeff.covey's message of Wed Jul 11 16:34:04 -0700 2007:
689 > some mail bounced, and when i went back to look in ~/.sup/sent.mbox, i
690 > found messages with "to:" lines like this:
691
692 This was due to a bug in svn revisions 473--491 in which multiple To: or
693 Cc: addresses would get squished together exactly in this manner. Sorry
694 about that! In r473 I switched to RubyMail composing the outgoing
695 message content, instead of doing it by hand, which was necessary for
696 attachment support. But I screwed up the headers in this manner.
697
698 > the problem seems to be traced back to these lines in
699 > ~/.sup/people.txt:
700
701 I think this is a symptom, not the problem itself. But you will have to
702 manually clean up people.txt now. Sorry. :(
703
704 Sent.mbox is an accurate reflection of whatever went out over the wire,
705 so you should be able to confirm that everything works with current
706 revisions by browsing it with mutt or whatever. (The same function is
707 called twice, once with an open stream to the sendmail process and again
708 with an file pointer to sent.mbox.) Let me know if you're still having
709 this problem with recent code.
710
711 --
712 William <wmorgan-sup at masanjin.net>
713
714 From wmorgan-sup@masanjin.net Tue Jul 17 21:42:41 2007
715 From: wmorgan-sup@masanjin.net (William Morgan)
716 Date: Tue, 17 Jul 2007 18:42:41 -0700
717 Subject: [sup-talk] [ANN] Sup 0.1 released
718 Message-ID: <1184722934-sup-4107@south>
719
720 Sup version 0.1 has been released!
721
722 http://sup.rubyforge.org
723
724 Sup is a console-based email client for people with a lot of email.
725 It supports tagging, very fast full-text search, automatic contact-
726 list management, and more. If you're the type of person who treats
727 email as an extension of your long-term memory, Sup is for you.
728
729 Changes:
730
731 == 0.1 / 2007-07-17
732 * MIME attachment creation.
733 * i18n support: character set conversion and rfc2047 header decoding.
734 * Better MIME handling.
735 * Multiple account support.
736 * Locking and concurrent Sup process detection and killation.
737 * Thread autoloading when you scroll down.
738 * Batch deletion of messages marked deleted or spam from message
739 sources via sup-sync-back tool (mbox only).
740 * Millions of bugfixes.
741
742 --
743 William <wmorgan-sup at masanjin.net>
744
745 From jeff.covey@pobox.com Wed Jul 18 18:21:17 2007
746 From: jeff.covey@pobox.com (jeff covey)
747 Date: Wed, 18 Jul 2007 18:21:17 -0400
748 Subject: [sup-talk] [ANN] Sup 0.1 released
749 In-Reply-To: <1184722934-sup-4107@south>
750 References: <1184722934-sup-4107@south>
751 Message-ID: <1184797247-sup-5066@mona>
752
753 Excerpts from William Morgan's message of Tue Jul 17 21:42:41 -0400 2007:
754
755 > Sup version 0.1 has been released!
756
757 congrats! :)
758
759 --
760 jeff covey
761 http://jeffcovey.net/
762
763
764 From wmorgan-sup@masanjin.net Thu Jul 19 14:01:06 2007
765 From: wmorgan-sup@masanjin.net (William Morgan)
766 Date: Thu, 19 Jul 2007 11:01:06 -0700
767 Subject: [sup-talk] [ANN] Sup 0.1 released
768 In-Reply-To: <1184797247-sup-5066@mona>
769 References: <1184722934-sup-4107@south> <1184797247-sup-5066@mona>
770 Message-ID: <1184867946-sup-8698@south>
771
772 Excerpts from jeff.covey's message of Wed Jul 18 15:21:17 -0700 2007:
773 > Excerpts from William Morgan's message of Tue Jul 17 21:42:41 -0400 2007:
774 > > Sup version 0.1 has been released!
775 > congrats! :)
776
777 Thanks! Here's my tentative plans for the next release:
778
779 Bug fixes:
780 - Brian's inbox bug
781 - Jeff's index.c:901 bug (There's a Ferret trac item for this now.)
782
783 Features:
784 - GPG support
785 - attachment forwarding
786 - maybe: tab-completion in to: and cc: for composing messages
787
788 Comments? Complaints?
789
790 --
791 William <wmorgan-sup at masanjin.net>
792
793 From nevans@mdlogix.com Thu Jul 19 14:18:58 2007
794 From: nevans@mdlogix.com (nicholas a. evans)
795 Date: Thu, 19 Jul 2007 14:18:58 -0400
796 Subject: [sup-talk] [ANN] Sup 0.1 released
797 In-Reply-To: <1184867946-sup-8698@south>
798 References: <1184722934-sup-4107@south> <1184797247-sup-5066@mona>
799 <1184867946-sup-8698@south>
800 Message-ID: <1184869044-sup-8195@nevans-desktop>
801
802 Excerpts from William Morgan's message of Thu Jul 19 14:01:06 -0400 2007:
803 > Features:
804 > - GPG support
805 > - attachment forwarding
806 > - maybe: tab-completion in to: and cc: for composing messages
807 >
808 > Comments? Complaints?
809
810 Could we get tab completion for setting labels? And also a keymapping to
811 set labels from thread-view-mode?
812
813 Thanks!
814
815
816 --
817 Nick
818
819 From wmorgan-sup@masanjin.net Thu Jul 19 14:55:45 2007
820 From: wmorgan-sup@masanjin.net (William Morgan)
821 Date: Thu, 19 Jul 2007 11:55:45 -0700
822 Subject: [sup-talk] [ANN] Sup 0.1 released
823 In-Reply-To: <1184869044-sup-8195@nevans-desktop>
824 References: <1184722934-sup-4107@south> <1184797247-sup-5066@mona>
825 <1184867946-sup-8698@south> <1184869044-sup-8195@nevans-desktop>
826 Message-ID: <1184871329-sup-6716@south>
827
828 Excerpts from nicholas a. evans's message of Thu Jul 19 11:18:58 -0700 2007:
829 > Could we get tab completion for setting labels? And also a keymapping
830 > to set labels from thread-view-mode?
831
832 Sure!
833
834 --
835 William <wmorgan-sup at masanjin.net>
836
837 From minciue@gmail.com Thu Jul 19 14:58:49 2007
838 From: minciue@gmail.com (Eugen Minciu)
839 Date: Thu, 19 Jul 2007 21:58:49 +0300
840 Subject: [sup-talk] [ANN] Sup 0.1 released
841 Message-ID: <1184871475-sup-2598@eugen-laptop>
842
843 Excerpts from nicholas a. evans's message of Thu Jul 19 21:18:58 +0300 2007:
844 > Excerpts from William Morgan's message of Thu Jul 19 14:01:06 -0400 2007:
845 > > Features:
846 > > - GPG support
847 > > - attachment forwarding
848 > > - maybe: tab-completion in to: and cc: for composing messages
849 > >
850 > > Comments? Complaints?
851 >
852 > Could we get tab completion for setting labels? And also a keymapping to
853 > set labels from thread-view-mode?
854 >
855 > Thanks!
856 >
857 >
858 Hi list!
859 Thanks for a wonderful program William. Here are a few of my desired
860 features:
861 - color schemes.
862 Somehow I'm not that fond of the defaults :) I know I can edit the code
863 but I'd like to be able to "theme" sup.
864
865 - incoming message filters
866 I'd like to be able to apply filters on incoming messages: label them,
867 archive some of them and so on
868
869 - polling with fetchmail
870 I use fetchmail and I'd like to be able to add some sort of hook before
871 polling that would run fetchmail first.
872
873 - moving archived articles to another mbox
874 This would be very useful because it would let me run biff programs.
875
876 I might be able to give you a hand (or patch) for one or two of these.
877 Which ones would you like and which would be the easiest?
878
879 Once again, thanks a lot,
880
881
882 --
883 Eugen Minciu.
884
885 Wasting valuable time since 1985.
886
887 From wmorgan-sup@masanjin.net Thu Jul 19 16:29:30 2007
888 From: wmorgan-sup@masanjin.net (William Morgan)
889 Date: Thu, 19 Jul 2007 13:29:30 -0700
890 Subject: [sup-talk] [ANN] Sup 0.1 released
891 In-Reply-To: <1184871475-sup-2598@eugen-laptop>
892 References: <1184871475-sup-2598@eugen-laptop>
893 Message-ID: <1184875869-sup-9220@south>
894
895 Hi Eugen,
896
897 Excerpts from Eugen Minciu's message of Thu Jul 19 11:58:49 -0700 2007:
898 > Thanks for a wonderful program William. Here are a few of my desired
899 > features:
900 > - color schemes.
901
902 On the todo list, along with customizable keybindings, but they're both
903 pretty far down. :)
904
905 > - incoming message filters
906 > I'd like to be able to apply filters on incoming messages: label them,
907 > archive some of them and so on
908
909 The way to do this currently is to use procmail to sort mail into
910 different folders, and then set labels, auto-archive/auto-read, etc. for
911 each source in Sup.
912
913 I realize that's not ideal (in particular, users whose mail is delivered
914 to IMAP servers not under their control are left out in the cold), but I
915 really really don't want to write a slow, buggy, Ruby procmail clone as
916 part of Sup.
917
918 Is there another option? I would really like the full power of procmail.
919
920 > - polling with fetchmail
921 > I use fetchmail and I'd like to be able to add some sort of hook before
922 > polling that would run fetchmail first.
923
924 I use fetchmail too, so I agree this would be nice. A near-term goal is
925 to have a good system of user-defined hooks, and I think this would be
926 the right place for that.
927
928 > - moving archived articles to another mbox
929 > This would be very useful because it would let me run biff programs.
930
931 This could be done easily, at least in a batch fashion, with a few
932 changes to sup-sync-back. I'm not sure if that's what you want. How do
933 you want to use biff with this?
934
935 (This reminds me that there is still a completely unresolved question of
936 how sup-sync-back should lock mboxes. It doesn't do any locking at all
937 currently, which means you should be probably very careful with it.)
938
939 > I might be able to give you a hand (or patch) for one or two of these.
940 > Which ones would you like and which would be the easiest?
941
942 If batch moving of archived messages is useful to you, that's probably
943 the easiest one to do.
944
945 Making the colors configurable wouldn't be too hard either. I'm
946 imagining a yaml config file that can override the color setup in
947 sup.rb. What do you think?
948
949 --
950 William <wmorgan-sup at masanjin.net>
951
952 From wmorgan-sup@masanjin.net Thu Jul 19 16:49:28 2007
953 From: wmorgan-sup@masanjin.net (William Morgan)
954 Date: Thu, 19 Jul 2007 13:49:28 -0700
955 Subject: [sup-talk] [ANN] Sup 0.1 released
956 Message-ID: <1184878159-sup-2212@south>
957
958 Excerpts from William Morgan's message of Thu Jul 19 13:29:30 -0700 2007:
959 > I realize that's not ideal (in particular, users whose mail is delivered
960 > to IMAP servers not under their control are left out in the cold), but I
961 > really really don't want to write a slow, buggy, Ruby procmail clone as
962 > part of Sup.
963 >
964 > Is there another option? I would really like the full power of procmail.
965
966 There is a way of tricking procmail into doing what I want. Sup could
967 take in a list of procmail rules and corresponding label assignments,
968 create a procmail configuration file that makes procmail act as a filter
969 that adds an X-Sup-Labels header with the corresponding labels, run all
970 new messages through procmail with that config file at poll time, and
971 then parse that header to determine the labels.
972
973 Pretty painful. But then you can just write some procmail rules for the
974 labels you want, and it doesn't matter what source the messages come
975 from (as long as you have procmail locally!).
976
977 --
978 William <wmorgan-sup at masanjin.net>
979
980 From daniel@electricrain.com Mon Jul 23 13:48:09 2007
981 From: daniel@electricrain.com (Dan Sully)
982 Date: Mon, 23 Jul 2007 10:48:09 -0700
983 Subject: [sup-talk] sup-sync & missing message-ids
984 Message-ID: <20070723174809.GA6866@electricrain.com>
985
986 For whatever reason, there are messages in my Maildir that don't have
987 message-ids in their headers. sup-sync bitches about that rather loudly..
988 would it be better to artificially construct a message-id?
989
990 Also, in the playing well with others category - sup doesn't seem to handle
991 the case where a message gets moved from Maildir/new/ to Maildir/cur/ if that
992 folder is read via IMAP from another client.. is this fixable in sup, or part
993 of the rubymail library?
994
995 Thanks
996
997 -D
998 --
999 <dsully> please describe web 2.0 to me in 2 sentences or less.
1000 <jwb> you make all the content. they keep all the revenue.
1001
1002 From daniel@electricrain.com Mon Jul 23 14:31:53 2007
1003 From: daniel@electricrain.com (Dan Sully)
1004 Date: Mon, 23 Jul 2007 11:31:53 -0700
1005 Subject: [sup-talk] Forward as attachment?
1006 Message-ID: <20070723183153.GA9853@electricrain.com>
1007
1008 Is there any way to forward an email as an rfc822 attachment currently?
1009
1010 Thanks
1011
1012 -D
1013 --
1014 <dsully> please describe web 2.0 to me in 2 sentences or less.
1015 <jwb> you make all the content. they keep all the revenue.
1016
1017 From daniel@electricrain.com Mon Jul 23 17:03:34 2007
1018 From: daniel@electricrain.com (Dan Sully)
1019 Date: Mon, 23 Jul 2007 14:03:34 -0700
1020 Subject: [sup-talk] sup errors with 0 messages in a folder
1021 Message-ID: <20070723210334.GA19236@electricrain.com>
1022
1023 If there is a maildir folder with 0 messages, sup will die:
1024
1025 lib/sup/source.rb:80:in `done?': undefined method `>=' for nil:NilClass
1026 (NoMethodError)
1027
1028 I've tried catching that in lib/sup/poll.rb, which works for sup-sync (to get
1029 it to "complete"), but the index isn't written out correctly, so sup proper
1030 thinks that folder is then out of sync.
1031
1032 -D
1033 --
1034 <dsully> please describe web 2.0 to me in 2 sentences or less.
1035 <jwb> you make all the content. they keep all the revenue.
1036
1037 From wmorgan-sup@masanjin.net Tue Jul 24 12:17:28 2007
1038 From: wmorgan-sup@masanjin.net (William Morgan)
1039 Date: Tue, 24 Jul 2007 09:17:28 -0700
1040 Subject: [sup-talk] Forward as attachment?
1041 In-Reply-To: <20070723183153.GA9853@electricrain.com>
1042 References: <20070723183153.GA9853@electricrain.com>
1043 Message-ID: <1185292420-sup-6934@south>
1044
1045 Hi Dan,
1046
1047 Excerpts from Dan Sully's message of Mon Jul 23 11:31:53 -0700 2007:
1048 > Is there any way to forward an email as an rfc822 attachment currently?
1049
1050 Not currently. You can manually attach messages by saving them to disk
1051 and attaching them as files, but they don't get mimed as rfc822.
1052 This is on the immediate todo list.
1053
1054 --
1055 William <wmorgan-sup at masanjin.net>
1056
1057 From wmorgan-sup@masanjin.net Tue Jul 24 13:52:56 2007
1058 From: wmorgan-sup@masanjin.net (William Morgan)
1059 Date: Tue, 24 Jul 2007 10:52:56 -0700
1060 Subject: [sup-talk] sup errors with 0 messages in a folder
1061 In-Reply-To: <20070723210334.GA19236@electricrain.com>
1062 References: <20070723210334.GA19236@electricrain.com>
1063 Message-ID: <1185299474-sup-18@south>
1064
1065 A non-text attachment was scrubbed...
1066 Name: a.patch
1067 Type: application/octet-stream
1068 Size: 446 bytes
1069 Desc: not available
1070 Url : http://rubyforge.org/pipermail/sup-talk/attachments/20070724/711d24a5/attachment-0001.obj
1071
1072 From wmorgan-sup@masanjin.net Tue Jul 24 13:56:01 2007
1073 From: wmorgan-sup@masanjin.net (William Morgan)
1074 Date: Tue, 24 Jul 2007 10:56:01 -0700
1075 Subject: [sup-talk] sup-sync & missing message-ids
1076 In-Reply-To: <20070723174809.GA6866@electricrain.com>
1077 References: <20070723174809.GA6866@electricrain.com>
1078 Message-ID: <1185299593-sup-1596@south>
1079
1080 Excerpts from Dan Sully's message of Mon Jul 23 10:48:09 -0700 2007:
1081 > For whatever reason, there are messages in my Maildir that don't have
1082 > message-ids in their headers. sup-sync bitches about that rather
1083 > loudly.. would it be better to artificially construct a message-id?
1084
1085 If this really is a prevalent thing, then yes, I'm happy to fake a
1086 message-id.
1087
1088 > Also, in the playing well with others category - sup doesn't seem to
1089 > handle the case where a message gets moved from Maildir/new/ to
1090 > Maildir/cur/ if that folder is read via IMAP from another client.. is
1091 > this fixable in sup, or part of the rubymail library?
1092
1093 This has nothing to do with RubyMail; Sup simply doesn't play well with
1094 other clients. Part of the tradeoff I made with Sup was to assume by
1095 default that the source never changes except through Sup. If that
1096 assumption fails, Sup should detect it and ask you to run sup-sync
1097 --changed, which should bring everything back in sync.
1098
1099 --
1100 William <wmorgan-sup at masanjin.net>
1101
1102 From daniel@electricrain.com Tue Jul 24 14:13:58 2007
1103 From: daniel@electricrain.com (Dan Sully)
1104 Date: Tue, 24 Jul 2007 11:13:58 -0700
1105 Subject: [sup-talk] sup-sync & missing message-ids
1106 In-Reply-To: <1185299593-sup-1596@south>
1107 References: <20070723174809.GA6866@electricrain.com>
1108 <1185299593-sup-1596@south>
1109 Message-ID: <20070724181358.GA20393@electricrain.com>
1110
1111 * William Morgan shaped the electrons to say...
1112
1113 >> For whatever reason, there are messages in my Maildir that don't have
1114 >> message-ids in their headers. sup-sync bitches about that rather
1115 >> loudly.. would it be better to artificially construct a message-id?
1116 >
1117 >If this really is a prevalent thing, then yes, I'm happy to fake a
1118 >message-id.
1119
1120 Yeah - I see it a lot. Also seeing mail with missing Date: headers. Most (but
1121 not all) is sent from automated systems, ie: order confirmation, etc.
1122
1123 I've attached a patch which is working for me with message-id.. a bit of a
1124 hack.
1125
1126 >This has nothing to do with RubyMail; Sup simply doesn't play well with
1127 >other clients. Part of the tradeoff I made with Sup was to assume by
1128 >default that the source never changes except through Sup. If that
1129 >assumption fails, Sup should detect it and ask you to run sup-sync
1130 >--changed, which should bring everything back in sync.
1131
1132 Yeah.. just a little inconvient if I'm checking mail via my iPhone then have
1133 to sup-sync before reading when I'm back in front of a terminal. Any issues
1134 with running sup-sync via cron ?
1135
1136 -D
1137 --
1138 <dsully> please describe web 2.0 to me in 2 sentences or less.
1139 <jwb> you make all the content. they keep all the revenue.
1140 -------------- next part --------------
1141 --- message.rb.orig 2007-07-23 11:16:12.000000000 -0700
1142 +++ message.rb 2007-07-23 11:42:15.000000000 -0700
1143 @@ -107,7 +107,8 @@
1144 def read_header header
1145 header.each { |k, v| header[k.downcase] = v }
1146
1147 - %w(message-id date).each do |f|
1148 + #%w(message-id date).each do |f|
1149 + %w(date).each do |f|
1150 raise MessageFormatError, "no #{f} field in header #{header.inspect} (source #@source offset #@source_info)" unless header.include? f
1151 raise MessageFormatError, "nil #{f} field in header #{header.inspect} (source #@source offset #@source_info)" unless header[f]
1152 end
1153 @@ -124,7 +125,7 @@
1154 @to = PersonManager.people_for header["to"]
1155 @cc = PersonManager.people_for header["cc"]
1156 @bcc = PersonManager.people_for header["bcc"]
1157 - @id = header["message-id"]
1158 + @id = header["message-id"] || header["from"].match(/\b(\S+?@\S+)\b/).captures.to_s + "." + @date.to_i.to_s
1159 @refs = (header["references"] || "").gsub(/[<>]/, "").split(/\s+/).flatten
1160 @replytos = (header["in-reply-to"] || "").scan(/<(.*?)>/).flatten
1161 @replyto = PersonManager.person_for header["reply-to"]
1162
1163 From daniel@electricrain.com Tue Jul 24 14:14:17 2007
1164 From: daniel@electricrain.com (Dan Sully)
1165 Date: Tue, 24 Jul 2007 11:14:17 -0700
1166 Subject: [sup-talk] sup errors with 0 messages in a folder
1167 In-Reply-To: <1185299474-sup-18@south>
1168 References: <20070723210334.GA19236@electricrain.com> <1185299474-sup-18@south>
1169 Message-ID: <20070724181417.GB20393@electricrain.com>
1170
1171 * William Morgan shaped the electrons to say...
1172
1173 >I don't have a good maildir testing setup any more. Can you try this
1174 >quick fix? (Going through this code again reminds me how I need to
1175 >rework it all...)
1176
1177 Yep - works much better than my hack did.
1178
1179 Thanks
1180
1181 -D
1182 --
1183 <dsully> please describe web 2.0 to me in 2 sentences or less.
1184 <jwb> you make all the content. they keep all the revenue.
1185
1186 From daniel@electricrain.com Tue Jul 24 14:26:03 2007
1187 From: daniel@electricrain.com (Dan Sully)
1188 Date: Tue, 24 Jul 2007 11:26:03 -0700
1189 Subject: [sup-talk] sup errors with 0 messages in a folder
1190 In-Reply-To: <20070724181417.GB20393@electricrain.com>
1191 References: <20070723210334.GA19236@electricrain.com> <1185299474-sup-18@south>
1192 <20070724181417.GB20393@electricrain.com>
1193 Message-ID: <20070724182603.GA22059@electricrain.com>
1194
1195 * Dan Sully shaped the electrons to say...
1196
1197 >Yep - works much better than my hack did.
1198
1199 Well, not quite. sup-sync now completes, but when running sup, I get:
1200
1201 Source: maildir:/home/daniel/mail/lists/perl/p5p/
1202 Error: Unknown message id 0.
1203 Fix: sup-sync --changed maildir:/home/daniel/mail/lists/perl/p5p/
1204
1205 And running that does not get rid of the message.
1206
1207 -D
1208 --
1209 <dsully> please describe web 2.0 to me in 2 sentences or less.
1210 <jwb> you make all the content. they keep all the revenue.
1211
1212 From wmorgan-sup@masanjin.net Tue Jul 24 18:14:59 2007
1213 From: wmorgan-sup@masanjin.net (William Morgan)
1214 Date: Tue, 24 Jul 2007 15:14:59 -0700
1215 Subject: [sup-talk] sup errors with 0 messages in a folder
1216 In-Reply-To: <20070724182603.GA22059@electricrain.com>
1217 References: <20070723210334.GA19236@electricrain.com> <1185299474-sup-18@south>
1218 <20070724181417.GB20393@electricrain.com>
1219 <20070724182603.GA22059@electricrain.com>
1220 Message-ID: <1185315278-sup-8521@south>
1221
1222 A non-text attachment was scrubbed...
1223 Name: a.patch
1224 Type: application/octet-stream
1225 Size: 1233 bytes
1226 Desc: not available
1227 Url : http://rubyforge.org/pipermail/sup-talk/attachments/20070724/25f8db5f/attachment.obj
1228
1229 From daniel@electricrain.com Tue Jul 24 18:22:44 2007
1230 From: daniel@electricrain.com (Dan Sully)
1231 Date: Tue, 24 Jul 2007 15:22:44 -0700
1232 Subject: [sup-talk] sup errors with 0 messages in a folder
1233 In-Reply-To: <1185315278-sup-8521@south>
1234 References: <20070723210334.GA19236@electricrain.com> <1185299474-sup-18@south>
1235 <20070724181417.GB20393@electricrain.com>
1236 <20070724182603.GA22059@electricrain.com>
1237 <1185315278-sup-8521@south>
1238 Message-ID: <20070724222244.GA3483@electricrain.com>
1239
1240 * William Morgan shaped the electrons to say...
1241
1242 >How about this one?
1243
1244 Better.. had to change the "check" to be "start = check"
1245
1246 -D
1247 --
1248 <dsully> please describe web 2.0 to me in 2 sentences or less.
1249 <jwb> you make all the content. they keep all the revenue.
1250
1251 From wmorgan-sup@masanjin.net Tue Jul 24 20:00:21 2007
1252 From: wmorgan-sup@masanjin.net (William Morgan)
1253 Date: Tue, 24 Jul 2007 17:00:21 -0700
1254 Subject: [sup-talk] sup errors with 0 messages in a folder
1255 In-Reply-To: <20070724222244.GA3483@electricrain.com>
1256 References: <20070723210334.GA19236@electricrain.com> <1185299474-sup-18@south>
1257 <20070724181417.GB20393@electricrain.com>
1258 <20070724182603.GA22059@electricrain.com>
1259 <1185315278-sup-8521@south>
1260 <20070724222244.GA3483@electricrain.com>
1261 Message-ID: <1185321598-sup-684@south>
1262
1263 Excerpts from Dan Sully's message of Tue Jul 24 15:22:44 -0700 2007:
1264 > Better.. had to change the "check" to be "start = check"
1265
1266 Good catch. Thanks. I'm going to rework these to be less horrendous in
1267 the near future.
1268
1269 --
1270 William <wmorgan-sup at masanjin.net>
1271
1272 From wmorgan-sup@masanjin.net Tue Jul 24 20:05:23 2007
1273 From: wmorgan-sup@masanjin.net (William Morgan)
1274 Date: Tue, 24 Jul 2007 17:05:23 -0700
1275 Subject: [sup-talk] sup-sync & missing message-ids
1276 In-Reply-To: <20070724181358.GA20393@electricrain.com>
1277 References: <20070723174809.GA6866@electricrain.com>
1278 <1185299593-sup-1596@south>
1279 <20070724181358.GA20393@electricrain.com>
1280 Message-ID: <1185321635-sup-1576@south>
1281
1282 Excerpts from Dan Sully's message of Tue Jul 24 11:13:58 -0700 2007:
1283 > I've attached a patch which is working for me with message-id.. a bit
1284 > of a hack.
1285
1286 Thanks. I've committed a modification of this. (I create the message-id by
1287 hashing the raw header text, which hopefully this should have all the nice
1288 uniqueness and consistency properties a message id should have.)
1289
1290 > Any issues with running sup-sync via cron ?
1291
1292 Shouldn't be, though that only works if you haven't used your iphone
1293 between the last cron run and when you invoke sup. Unless the folder is
1294 really large, you might instead consider running sup-sync immediately
1295 before running Sup and considering it an annoying startup delay. :)
1296
1297 --
1298 William <wmorgan-sup at masanjin.net>
1299
1300 From wmorgan-sup@masanjin.net Tue Jul 24 20:31:15 2007
1301 From: wmorgan-sup@masanjin.net (William Morgan)
1302 Date: Tue, 24 Jul 2007 17:31:15 -0700
1303 Subject: [sup-talk] new in svn: alias expansion in searches
1304 Message-ID: <1185323404-sup-1108@south>
1305
1306 Searching for to:mom, from:bob, etc. now works. You don't have to type
1307 out the whole email address any more.
1308
1309 --
1310 William <wmorgan-sup at masanjin.net>
1311
1312 From daniel@electricrain.com Wed Jul 25 11:04:11 2007
1313 From: daniel@electricrain.com (Dan Sully)
1314 Date: Wed, 25 Jul 2007 08:04:11 -0700
1315 Subject: [sup-talk] The 'd' key, and other suggestions
1316 Message-ID: <1185375587-sup-5023@zap.electricrain.com>
1317
1318 Perhaps my fingers haven't been retrained quite yet, but two things I've
1319 noticed while going through my mail this morning:
1320
1321 'D' in the inbox seems like a poor choice - I've twice now reverted my state.
1322
1323 'd' while looking at a message doesn't have the behavior I thought it would
1324 (being so close to mutt in other ways), of deleting the current message and
1325 moving onto the next one.
1326
1327 Also when composing a mail, I find Mutt's prompting of To & Subject very
1328 helpful before being dumped into the editor (below the subject line as well).
1329
1330 Just noticed another slight bug - I just suspending this process (^Z), and
1331 then fg'd it - cursing is a bit wrong, it placed me back in the "Reply to
1332 Sender / Reply to Mail list / Reply to All' screen, instead of my editor.
1333 Thankfully a ^L fixed that.
1334
1335 -D
1336 --
1337 <dsully> please describe web 2.0 to me in 2 sentences or less.
1338 <jwb> you make all the content. they keep all the revenue.
1339
1340 --
1341
1342 -D
1343 --
1344 <dsully> please describe web 2.0 to me in 2 sentences or less.
1345 <jwb> you make all the content. they keep all the revenue.
1346
1347 From daniel@electricrain.com Wed Jul 25 11:34:29 2007
1348 From: daniel@electricrain.com (Dan Sully)
1349 Date: Wed, 25 Jul 2007 08:34:29 -0700
1350 Subject: [sup-talk] Unicode
1351 Message-ID: <1185377570-sup-5514@zap.electricrain.com>
1352
1353 I know Unicode support in Ruby is.. lacking. But is there anything I can do to
1354 prevent the dreaded unicode question marks (often followed by a tilde), which
1355 totally destroy the curses layout.
1356
1357 I see that iconv is being used in sup, but I'm not sure when/why.
1358
1359 Thanks.
1360
1361 -D
1362 --
1363 <dsully> please describe web 2.0 to me in 2 sentences or less.
1364 <jwb> you make all the content. they keep all the revenue.
1365
1366 --
1367
1368 -D
1369 --
1370 <dsully> please describe web 2.0 to me in 2 sentences or less.
1371 <jwb> you make all the content. they keep all the revenue.
1372
1373 From wmorgan-sup@masanjin.net Wed Jul 25 13:42:38 2007
1374 From: wmorgan-sup@masanjin.net (William Morgan)
1375 Date: Wed, 25 Jul 2007 10:42:38 -0700
1376 Subject: [sup-talk] Unicode
1377 In-Reply-To: <1185377570-sup-5514@zap.electricrain.com>
1378 References: <1185377570-sup-5514@zap.electricrain.com>
1379 Message-ID: <1185385187-sup-767@south>
1380
1381 Excerpts from Dan Sully's message of Wed Jul 25 08:34:29 -0700 2007:
1382 > I know Unicode support in Ruby is.. lacking. But is there anything I
1383 > can do to prevent the dreaded unicode question marks (often followed
1384 > by a tilde), which totally destroy the curses layout.
1385
1386 Here's what has worked for me:
1387
1388 1. Use gnome-terminal
1389 2. set LANG=en_US.UTF-8
1390
1391 Then, somehow, magically, using ncurses to display utf8 characters just
1392 works. Well, I haven't tried wide characters, but accented characters
1393 work.
1394
1395 > I see that iconv is being used in sup, but I'm not sure when/why.
1396
1397 Sup uses iconv to convert messages (and individual headers) marked as
1398 in specific encodings to your local encoding, as determined by LC_CTYPE
1399 and LANG environment variables.
1400
1401 What *doesn't* work right now is calculating the lengths of unicode
1402 strings, so the display is a little screwed up for characters that take
1403 more than one utf-8 byte. But still usable.
1404
1405 --
1406 William <wmorgan-sup at masanjin.net>
1407
1408 From daniel@electricrain.com Wed Jul 25 13:54:23 2007
1409 From: daniel@electricrain.com (Dan Sully)
1410 Date: Wed, 25 Jul 2007 10:54:23 -0700
1411 Subject: [sup-talk] Unicode
1412 In-Reply-To: <1185385187-sup-767@south>
1413 References: <1185377570-sup-5514@zap.electricrain.com>
1414 <1185385187-sup-767@south>
1415 Message-ID: <1185385955-sup-2860@zap.electricrain.com>
1416
1417 > Here's what has worked for me:
1418 >
1419 > 1. Use gnome-terminal
1420 > 2. set LANG=en_US.UTF-8
1421
1422 I'm using LANG, but with xterm-color (via Terminal.app to a Ubuntu box). That
1423 setup works fine for Mutt, fyi.
1424
1425 I'll wait for another full wide subject line to come in, but the other ones
1426 have been Windows encoded quotes and the like.
1427
1428 > What *doesn't* work right now is calculating the lengths of unicode
1429 > strings, so the display is a little screwed up for characters that take
1430 > more than one utf-8 byte. But still usable.
1431
1432 Ok, that would make sense.
1433
1434 --
1435
1436 -D
1437 --
1438 <dsully> please describe web 2.0 to me in 2 sentences or less.
1439 <jwb> you make all the content. they keep all the revenue.
1440
1441 From wmorgan-sup@masanjin.net Wed Jul 25 14:50:47 2007
1442 From: wmorgan-sup@masanjin.net (William Morgan)
1443 Date: Wed, 25 Jul 2007 11:50:47 -0700
1444 Subject: [sup-talk] Unicode
1445 In-Reply-To: <1185385955-sup-2860@zap.electricrain.com>
1446 References: <1185377570-sup-5514@zap.electricrain.com>
1447 <1185385187-sup-767@south>
1448 <1185385955-sup-2860@zap.electricrain.com>
1449 Message-ID: <1185388707-sup-1409@south>
1450
1451 Excerpts from Dan Sully's message of Wed Jul 25 10:54:23 -0700 2007:
1452 > I'm using LANG, but with xterm-color (via Terminal.app to a Ubuntu
1453 > box). That setup works fine for Mutt, fyi.
1454
1455 If you cat out a utf-8 file, does the terminal display the right thing?
1456 If so, I would think that would work for Sup... at least under my
1457 current mental model where ncurses doesn't do anything except put out
1458 raw bytes which the terminal interprets.
1459
1460 > > What *doesn't* work right now is calculating the lengths of unicode
1461 > > strings, so the display is a little screwed up for characters that
1462 > > take more than one utf-8 byte. But still usable.
1463 >
1464 > Ok, that would make sense.
1465
1466 And in fact it's actually only a problem in thread-index-mode when
1467 someone's name is a rfc2047-encoded header. In every other case there's
1468 no character alignment issue. :)
1469
1470
1471 --
1472 William <wmorgan-sup at masanjin.net>
1473
1474 From daniel@electricrain.com Wed Jul 25 15:00:24 2007
1475 From: daniel@electricrain.com (Dan Sully)
1476 Date: Wed, 25 Jul 2007 12:00:24 -0700
1477 Subject: [sup-talk] Unicode
1478 In-Reply-To: <1185388707-sup-1409@south>
1479 References: <1185377570-sup-5514@zap.electricrain.com>
1480 <1185385187-sup-767@south>
1481 <1185385955-sup-2860@zap.electricrain.com>
1482 <1185388707-sup-1409@south>
1483 Message-ID: <1185389999-sup-7964@zap.electricrain.com>
1484
1485 > If you cat out a utf-8 file, does the terminal display the right thing?
1486 > If so, I would think that would work for Sup... at least under my
1487 > current mental model where ncurses doesn't do anything except put out
1488 > raw bytes which the terminal interprets.
1489
1490 Yep, it displays the right thing. I'll try and get you more data.
1491
1492 --
1493
1494 -D
1495 --
1496 <dsully> please describe web 2.0 to me in 2 sentences or less.
1497 <jwb> you make all the content. they keep all the revenue.
1498
1499 From daniel@electricrain.com Wed Jul 25 15:01:47 2007
1500 From: daniel@electricrain.com (Dan Sully)
1501 Date: Wed, 25 Jul 2007 12:01:47 -0700
1502 Subject: [sup-talk] Yes/No Send prompt missing
1503 Message-ID: <1185390033-sup-7568@zap.electricrain.com>
1504
1505 After using my $EDITOR (vim), to reply/compose a new message, I quit from it,
1506 and sup drops me back to where I was before. There's no Yes/No/Postpone prompt
1507 for sending the message. However, if I hit 'y', the message is sent.
1508
1509 --
1510
1511 -D
1512 --
1513 <dsully> please describe web 2.0 to me in 2 sentences or less.
1514 <jwb> you make all the content. they keep all the revenue.
1515
1516 From wmorgan-sup@masanjin.net Thu Jul 26 01:45:08 2007
1517 From: wmorgan-sup@masanjin.net (William Morgan)
1518 Date: Wed, 25 Jul 2007 22:45:08 -0700
1519 Subject: [sup-talk] The 'd' key, and other suggestions
1520 In-Reply-To: <1185375587-sup-5023@zap.electricrain.com>
1521 References: <1185375587-sup-5023@zap.electricrain.com>
1522 Message-ID: <1185428082-sup-7118@south>
1523
1524 Hi Dan,
1525
1526 Excerpts from Dan Sully's message of Wed Jul 25 08:04:11 -0700 2007:
1527 > 'D' in the inbox seems like a poor choice - I've twice now reverted my
1528 > state.
1529 >
1530 > 'd' while looking at a message doesn't have the behavior I thought it
1531 > would (being so close to mutt in other ways), of deleting the current
1532 > message and moving onto the next one.
1533
1534 I can change the default mappings, but then everyone else would have to
1535 retrain their fingers. Maybe you could make a case for 'D'. Do other
1536 ex-mutt users have this problem? (In general mutt keystroke
1537 compatibility is not really my priority, but I do recognize my target
1538 audience here.)
1539
1540 In the future keybindings will be configurable, but that's pretty far
1541 down on the list at the moment.
1542
1543 > Also when composing a mail, I find Mutt's prompting of To & Subject
1544 > very helpful before being dumped into the editor (below the subject
1545 > line as well).
1546
1547 I do plan to have Sup prompt you for To: so that you can have tab
1548 completion. I'm not so sure about Subject though. In general I like to
1549 keep stuff in the editor as much as possible because that's a far better
1550 place to edit text than my shitty ncurses readline emulator.
1551
1552 Cursor positioning to below Subject: is editor-specific. With vi I
1553 think you can use something like -c '/^$'.
1554
1555 > Just noticed another slight bug - I just suspending this process (^Z),
1556 > and then fg'd it - cursing is a bit wrong, it placed me back in the
1557 > "Reply to Sender / Reply to Mail list / Reply to All' screen, instead
1558 > of my editor.
1559
1560 Yeah, this is a known problem and I have no idea how to fix it. In fact
1561 sometimes curses is just completely crazy after a suspend and I can't
1562 get it to do anything sensible and have to ^C. No idea.
1563
1564 --
1565 William <wmorgan-sup at masanjin.net>
1566
1567 From wmorgan-sup@masanjin.net Thu Jul 26 01:47:22 2007
1568 From: wmorgan-sup@masanjin.net (William Morgan)
1569 Date: Wed, 25 Jul 2007 22:47:22 -0700
1570 Subject: [sup-talk] Yes/No Send prompt missing
1571 In-Reply-To: <1185390033-sup-7568@zap.electricrain.com>
1572 References: <1185390033-sup-7568@zap.electricrain.com>
1573 Message-ID: <1185428715-sup-8781@south>
1574
1575 Excerpts from Dan Sully's message of Wed Jul 25 12:01:47 -0700 2007:
1576 > After using my $EDITOR (vim), to reply/compose a new message, I quit
1577 > from it, and sup drops me back to where I was before. There's no
1578 > Yes/No/Postpone prompt for sending the message. However, if I hit 'y',
1579 > the message is sent.
1580
1581 Post-edit you're back in compose mode where you can attach stuff,
1582 postpone, discard, send, etc. The send command happens to be 'y', same
1583 as mutt. No yes/no prompt required.
1584
1585 --
1586 William <wmorgan-sup at masanjin.net>
1587
1588 From jeff.covey@pobox.com Thu Jul 26 12:46:52 2007
1589 From: jeff.covey@pobox.com (jeff covey)
1590 Date: Thu, 26 Jul 2007 12:46:52 -0400
1591 Subject: [sup-talk] The 'd' key, and other suggestions
1592 In-Reply-To: <1185428082-sup-7118@south>
1593 References: <1185375587-sup-5023@zap.electricrain.com>
1594 <1185428082-sup-7118@south>
1595 Message-ID: <1185467966-sup-4811@mona>
1596
1597 Excerpts from William Morgan's message of Thu Jul 26 01:45:08 -0400 2007:
1598
1599 > Maybe you could make a case for 'D'. Do other ex-mutt users have this
1600 > problem?
1601
1602 i do find it awkward when i'm processing my inbox and want to delete the
1603 thread i'm reading and move to the next new one. i have to hit "x", "d",
1604 "tab", "enter", and that adds up to an annoyance after the first twenty
1605 times. it would be great if one keystroke did it all.
1606
1607 "h" seems to be unused in thread-view-mode. would it be a better choice for
1608 "toggle detailed header", with "d" triggering something like "delete the
1609 current thread and open the next new thread in the previous buffer"? in
1610 other words, if you've done a search on "foo", opened a thread from the
1611 search, and hit "d", sup would delete the thread being viewed, close its
1612 buffer, and look for and open the next unread thread in the "foo" search
1613 buffer (or just go to the "foo" search buffer if there's nothing unread in
1614 it). too complicated?
1615
1616 thanks,
1617
1618 --
1619 jeff covey
1620 http://jeffcovey.net/
1621
1622
1623 From nevans@mdlogix.com Thu Jul 26 13:45:56 2007
1624 From: nevans@mdlogix.com (nicholas a. evans)
1625 Date: Thu, 26 Jul 2007 13:45:56 -0400
1626 Subject: [sup-talk] The 'd' key, and other suggestions
1627 In-Reply-To: <1185467966-sup-4811@mona>
1628 References: <1185375587-sup-5023@zap.electricrain.com>
1629 <1185428082-sup-7118@south> <1185467966-sup-4811@mona>
1630 Message-ID: <1185471532-sup-4914@nevans-desktop>
1631
1632 Excerpts from jeff.covey's message of Thu Jul 26 12:46:52 -0400 2007:
1633 > Excerpts from William Morgan's message of Thu Jul 26 01:45:08 -0400 2007:
1634 >
1635 > > Maybe you could make a case for 'D'. Do other ex-mutt users have this
1636 > > problem?
1637 >
1638 > i do find it awkward when i'm processing my inbox and want to delete the
1639 > thread i'm reading and move to the next new one. i have to hit "x", "d",
1640 > "tab", "enter", and that adds up to an annoyance after the first twenty
1641 > times. it would be great if one keystroke did it all.
1642
1643 Since we're on the subject of keybindings, my other pet peeve: "a" versus
1644 "A", in thread-view-mode. Because index-view-mode uses "a", I press that in
1645 thread-view-mode expecting to have the thread archived. For some reason, I
1646 can never seem to remember to use "A" instead.
1647
1648 So, I generally do: "a", "^G", "A".
1649 Or sometimes: "a", "^G", "x", "a".
1650 Or sometimes: <sit... think about it... hmmm...>, "A".
1651
1652 Muscle memory is no good for that keybinding. ;-)
1653
1654 In general, if there is a command that operates on a message from index mode
1655 and makes sense to also operate in thread-view-mode, it would be useful if
1656 they had the same keybinding.
1657
1658 --
1659 Nick
1660