community/pipermail-archives/sup-talk/2008-08.txt (64862B) - raw
1 From wmorgan-sup@masanjin.net Fri Aug 1 16:45:35 2008
2 From: wmorgan-sup@masanjin.net (William Morgan)
3 Date: Fri, 01 Aug 2008 13:45:35 -0700
4 Subject: [sup-talk] colors in 0.6
5 In-Reply-To: <1217545348-sup-5151@wrasse>
6 References: <1217545348-sup-5151@wrasse>
7 Message-ID: <1217623461-sup-3156@entry>
8
9 Reformatted excerpts from Richard Heycock's message of 2008-07-31:
10 > :colors:
11 > :index_new:
12 > :bg: yellow
13 >
14 > <snip>
15 >
16 > But it still comes up the default colour scheme.
17 >
18 > I know the file is being read (using strace) so I'm guessing it's a
19 > problem with the yaml. Any ideas?
20
21 You just need to remove the :colors: line. It's expecting something
22 like:
23
24 ---
25 :index_new:
26 :bg: yellow
27
28 HTH,
29 --
30 William <wmorgan-sup at masanjin.net>
31
32 From kramert@informatik.uni-freiburg.de Sun Aug 3 19:17:28 2008
33 From: kramert@informatik.uni-freiburg.de (Thorsten Kramer)
34 Date: Mon, 04 Aug 2008 01:17:28 +0200
35 Subject: [sup-talk] Beginner questions
36 Message-ID: <1217805086-sup-749@pluto>
37
38 Hi,
39
40 recently I switched from mutt to sup. Everything works fine besides some
41 minor issues:
42
43 1) Unfortunately, the gpg integration doesn't work. If I want to sign my mails,
44 sup complains about: 'Problem sending mail: gpg: gpg-agent is not available in
45 this session' Any tipps to avoid this? With mutt, gpg works fine.
46
47 2) I've configured several accounts for sending mail. How can I switch
48 between them in the mail-compose view? Is changing the from address the
49 only way?
50
51 3) In mutt you can define macros. E.g. you press F2 and the
52 selected mail is moved from its maildir to a spam mbox. Is this
53 possible with sup?
54
55 Thanks!
56
57 From wmorgan-sup@masanjin.net Sun Aug 3 21:41:54 2008
58 From: wmorgan-sup@masanjin.net (William Morgan)
59 Date: Sun, 03 Aug 2008 18:41:54 -0700
60 Subject: [sup-talk] Beginner questions
61 In-Reply-To: <1217805086-sup-749@pluto>
62 References: <1217805086-sup-749@pluto>
63 Message-ID: <1217813913-sup-4564@entry>
64
65 Hi Thorsten,
66
67 Reformatted excerpts from Thorsten Kramer's message of 2008-08-03:
68 > recently I switched from mutt to sup.
69
70 Welcome!
71
72 > 1) Unfortunately, the gpg integration doesn't work. If I want to sign
73 > my mails, sup complains about: 'Problem sending mail: gpg: gpg-agent
74 > is not available in this session' Any tipps to avoid this? With mutt,
75 > gpg works fine.
76
77 At least right now, the only way to run Sup with GPG is to use
78 gpg-agent. Sup doesn't ask for your password, store it, expire it, etc.
79 So you'll need to start gpg-agent in the background, and then gpg should
80 automatically trigger it to ask you for your password.
81
82 The one problem with this so far is that the curses version of gpg-agent
83 doesn't interact well with Sup. If you're using the X version, you'll be
84 fine.
85
86 > 2) I've configured several accounts for sending mail. How can I switch
87 > between them in the mail-compose view? Is changing the from address
88 > the only way?
89
90 Yes, that's the only way. (So far!)
91
92 > 3) In mutt you can define macros. E.g. you press F2 and the selected
93 > mail is moved from its maildir to a spam mbox. Is this possible with
94 > sup?
95
96 No. I would like to have this at some point, and I don't think it would
97 be terribly hard, but right now even the keybindings are not
98 configurable.
99 --
100 William <wmorgan-sup at masanjin.net>
101
102 From wmorgan-sup@masanjin.net Mon Aug 4 00:08:18 2008
103 From: wmorgan-sup@masanjin.net (William Morgan)
104 Date: Sun, 03 Aug 2008 21:08:18 -0700
105 Subject: [sup-talk] [ANN] Sup 0.6 Released
106 Message-ID: <1217822888-sup-2959@entry>
107
108 Sup version 0.6 has been released!
109
110 * <http://sup.rubyforge.org>
111
112 Sup is a console-based email client for people with a lot of email.
113 It supports tagging, very fast full-text search, automatic contact-
114 list management, and more. If you're the type of person who treats
115 email as an extension of your long-term memory, Sup is for you.
116
117 Sup makes it easy to:
118 - Handle massive amounts of email.
119
120 - Mix email from different sources: mbox files (even across different
121 machines), Maildir directories, IMAP folders, POP accounts, and
122 GMail accounts.
123
124 - Instantaneously search over your entire email collection. Search
125 over body text, or use a query language to combine search
126 predicates in any way.
127
128 - Handle multiple accounts. Replying to email sent to a particular
129 account will use the correct SMTP server, signature, and from
130 address.
131
132 - Add custom code to handle certain types of messages or to handle
133 certain types of text within messages.
134
135 - Organize email with user-defined labels, automatically track
136 recent contacts, and much more!
137
138 The goal of Sup is to become the email client of choice for nerds
139 everywhere.
140
141 Changes:
142
143 ## 0.6 / 2008-08-04
144 * new hooks: mark-as-spam, reply-to, reply-from
145 * configurable colors. finally!
146 * many bugfixes
147 * more vi keys added, and 'q' now asks before quitting
148 * attachment markers (little @ signs!) in thread-index-mode
149 * maildir speedups
150 * attachment name searchability
151 * archive-and-mark-read command in inbox-mode
152
153 * <http://sup.rubyforge.org>
154 --
155 William <wmorgan-sup at masanjin.net>
156
157 From cj.fleck@gmail.com Mon Aug 4 11:05:28 2008
158 From: cj.fleck@gmail.com (CJ Fleck)
159 Date: Mon, 4 Aug 2008 11:05:28 -0400
160 Subject: [sup-talk] Sending mail
161 Message-ID: <12258ab10808040805q39aabf26lb7711dee88f2527b@mail.gmail.com>
162
163 I'm trying out sup v 0.6, and I'm stuck when I go to send mail. I use
164 msmtp and '/usr/bin/msmtp --account=foo me at someaddress.com < filename'
165 works from the command line. In my config.yaml, I have a ':sendmail:
166 /usr/bin/msmtp --account=foo -t'.
167
168 The problem arises, when I compose the mail, and I go to exit the
169 editor, it brings me to the "Crypto" buffer. I choose none, and it
170 immediately goes back to the editor. This is a cycle I cannot break.
171 Am I missing something here? How do I send the mail?
172
173 CJ
174
175 From wmorgan-sup@masanjin.net Mon Aug 4 11:31:14 2008
176 From: wmorgan-sup@masanjin.net (William Morgan)
177 Date: Mon, 04 Aug 2008 08:31:14 -0700
178 Subject: [sup-talk] Sending mail
179 In-Reply-To: <12258ab10808040805q39aabf26lb7711dee88f2527b@mail.gmail.com>
180 References: <12258ab10808040805q39aabf26lb7711dee88f2527b@mail.gmail.com>
181 Message-ID: <1217863726-sup-1263@entry>
182
183 Reformatted excerpts from CJ Fleck's message of 2008-08-04:
184 > The problem arises, when I compose the mail, and I go to exit the
185 > editor, it brings me to the "Crypto" buffer. I choose none, and it
186 > immediately goes back to the editor. This is a cycle I cannot break.
187 > Am I missing something here? How do I send the mail?
188
189 This might just be a UI issue. I think what you're calling the "crypto
190 buffer" is the reply composition buffer. Pressing enter dumps you into
191 the editor, and exiting the editor brings you back there. You can move
192 the row cursor with the up and down arrows, and you can press 'y' to
193 actually send the email. Weird, perhaps, but that's part of the mutt
194 legacy, and one day Sup will have configurable keymaps.
195 --
196 William <wmorgan-sup at masanjin.net>
197
198 From marc.hartstein@alum.vassar.edu Mon Aug 4 11:25:08 2008
199 From: marc.hartstein@alum.vassar.edu (Marc Hartstein)
200 Date: Mon, 04 Aug 2008 11:25:08 -0400
201 Subject: [sup-talk] Sending mail
202 In-Reply-To: <12258ab10808040805q39aabf26lb7711dee88f2527b@mail.gmail.com>
203 References: <12258ab10808040805q39aabf26lb7711dee88f2527b@mail.gmail.com>
204 Message-ID: <1217863372-sup-8273@cabinet>
205
206 Excerpts from CJ Fleck's message of Mon Aug 04 11:05:28 -0400 2008:
207 > The problem arises, when I compose the mail, and I go to exit the
208 > editor, it brings me to the "Crypto" buffer. I choose none, and it
209 > immediately goes back to the editor. This is a cycle I cannot break.
210 > Am I missing something here? How do I send the mail?
211
212 Unless it's changed from 'next' as of a couple of months ago to 0.6:
213
214 Press <y> to send mail (like in mutt); <Enter> edits the message. I've
215 also found that slightly confusing at times, because you're manipulating
216 something which looks like a menu, so you expect <Enter> to do the
217 "obvious" thing and confirm (sending).
218
219 If it has change, press <?> on that screen to see the key bindings.
220
221 From kramert@informatik.uni-freiburg.de Tue Aug 5 17:52:25 2008
222 From: kramert@informatik.uni-freiburg.de (Thorsten Kramer)
223 Date: Tue, 05 Aug 2008 23:52:25 +0200
224 Subject: [sup-talk] Beginner questions
225 In-Reply-To: <1217813913-sup-4564@entry>
226 References: <1217805086-sup-749@pluto> <1217813913-sup-4564@entry>
227 Message-ID: <1217972659-sup-8094@pluto>
228
229 Hi William,
230
231 Excerpts from William Morgan's message of Mon Aug 04 03:41:54 +0200 2008:
232
233 > The one problem with this so far is that the curses version of gpg-agent
234 > doesn't interact well with Sup. If you're using the X version, you'll be
235 > fine.
236
237 Well, it's strange. Sometimes the gpg-agent reacts, sometimes the
238 running daemon isn't recognized. Anyway, it's definitely a problem
239 caused by my gpg installation, not by sup.
240
241 > No. I would like to have this at some point, and I don't think it would
242 > be terribly hard, but right now even the keybindings are not
243 > configurable.
244
245 OK. Then the mark-as-spam hook will probably do for me.
246
247
248 Best regards,
249 Thorsten
250
251 From kendall@clarkparsia.com Tue Aug 5 18:57:57 2008
252 From: kendall@clarkparsia.com (Kendall Grant Clark)
253 Date: Tue, 05 Aug 2008 18:57:57 -0400
254 Subject: [sup-talk] sup doesn't like '[Gmail]' in maildir URI
255 Message-ID: <1217976772-sup-7788@k-desktop.int.clarkparsia.com>
256
257 Folks,
258
259 I just switched email to Gmail; so far, so good. I use offlineimap to grab
260 [Gmail] and INBOX; but when I add a maildir URI with sup-add that includes
261 the path component '[Gmail]', it bitches about illegal URI.
262
263 So I encoded the '[' and ']' characters -- would be nice if sup-add offered to
264 do that automagically -- but then sup-add bitches about ~/path/%5BGmail%5D/cur
265 not being a director, when of course it *is* a directory... Leads me to
266 believe there's still something wrong with the encoded [Gmail] bit, since
267 ~/path/INBOX works fine.
268
269 Has anyone else seen and solved this problem? I'm using sup 0.6, which is
270 otherwise excellent.
271
272 Cheers,
273 Kendall Clark
274
275 From its.jeff.balogh@gmail.com Tue Aug 5 19:17:12 2008
276 From: its.jeff.balogh@gmail.com (Jeff Balogh)
277 Date: Tue, 05 Aug 2008 19:17:12 -0400
278 Subject: [sup-talk] sup doesn't like '[Gmail]' in maildir URI
279 In-Reply-To: <1217976772-sup-7788@k-desktop.int.clarkparsia.com>
280 References: <1217976772-sup-7788@k-desktop.int.clarkparsia.com>
281 Message-ID: <1217977678-sup-288@archie>
282
283 Kendall Grant Clark wrote:
284 > Folks,
285 >
286 > I just switched email to Gmail; so far, so good. I use offlineimap to grab
287 > [Gmail] and INBOX; but when I add a maildir URI with sup-add that includes
288 > the path component '[Gmail]', it bitches about illegal URI.
289 >
290 > So I encoded the '[' and ']' characters -- would be nice if sup-add offered to
291 > do that automagically -- but then sup-add bitches about ~/path/%5BGmail%5D/cur
292 > not being a director, when of course it *is* a directory... Leads me to
293 > believe there's still something wrong with the encoded [Gmail] bit, since
294 > ~/path/INBOX works fine.
295 >
296 > Has anyone else seen and solved this problem? I'm using sup 0.6, which is
297 > otherwise excellent.
298
299 For Gmail, you probably want to just grab the 'All Mail' folder. All your mail
300 goes there (imagine that!), so tracking INBOX is unnecessary. Especially since
301 sup will complain if you ever clear out the inbox.
302
303 To get around the URI problem, I use `nametrans` in ~/.offlineimaprc to clean up
304 the folder names:
305
306 nametrans = lambda s: s.replace('[','').replace(']','').replace(' ', '_')
307
308 In English, remove brackets and turn spaces into underscores.
309
310 Cheers,
311 jeff
312
313 From daniel.neubacher@xing.com Wed Aug 6 08:24:01 2008
314 From: daniel.neubacher@xing.com (Daniel Neubacher)
315 Date: Wed, 06 Aug 2008 14:24:01 +0200
316 Subject: [sup-talk] safe index in the after-poll.rb ?
317 Message-ID: <1218025176-sup-6853@daniel-laptop>
318
319 Hello there,
320 i've build me a after-poll hook to display the unread mail count in my
321 window manager:
322 system ("echo 0 widget_tell mystatusbar mails text
323 \\|#{num_inbox_total_unread}\\| | awesome-client")
324
325 This is working, but only when the index is safed. When i read some
326 mails and do not safe the index the count doesnt give me the right
327 amount of unread mails back. So is there a way to save the index
328 automaticly after polling my mails ?
329
330 thanks in advance
331 Daniel Neubacher
332
333 From kendall@clarkparsia.com Wed Aug 6 09:38:49 2008
334 From: kendall@clarkparsia.com (Kendall Clark)
335 Date: Wed, 6 Aug 2008 09:38:49 -0400
336 Subject: [sup-talk] sup doesn't like '[Gmail]' in maildir URI
337 In-Reply-To: <1217977678-sup-288@archie>
338 References: <1217976772-sup-7788@k-desktop.int.clarkparsia.com>
339 <1217977678-sup-288@archie>
340 Message-ID: <1fc9c2ff0808060638x3eea84beud71186f79488dbe8@mail.gmail.com>
341
342 On Tue, Aug 5, 2008 at 7:17 PM, Jeff Balogh <its.jeff.balogh at gmail.com> wrote:
343 > For Gmail, you probably want to just grab the 'All Mail' folder. All your mail
344 > goes there (imagine that!), so tracking INBOX is unnecessary. Especially since
345 > sup will complain if you ever clear out the inbox.
346 >
347 > To get around the URI problem, I use `nametrans` in ~/.offlineimaprc to clean up
348 > the folder names:
349 >
350 > nametrans = lambda s: s.replace('[','').replace(']','').replace(' ', '_')
351 >
352 > In English, remove brackets and turn spaces into underscores.
353
354 Thanks, Jeff -- both suggestions worked nicely.
355
356 Cheers,
357 Kendall
358
359 From johnbent@lanl.gov Wed Aug 6 10:12:41 2008
360 From: johnbent@lanl.gov (John Bent)
361 Date: Wed, 06 Aug 2008 08:12:41 -0600
362 Subject: [sup-talk] two sup crashes
363 Message-ID: <1218031573-sup-325@tangerine.lanl.gov>
364
365 I was sending an email and sup crashed. I restarted, resent the email,
366 and then it crashed again right after I archived some emails, saved the
367 index and tried to refresh my screen. Both errors are below and seem to
368 be related.
369
370 --- EOFError from thread: main
371 End-of-File Error occured at <except.c>:93 in xraise
372 Error occured in compound_io.c:137 - cmpdi_read_i
373 Tried to read past end of file. File length is <1> and tried to read
374 to <162169>
375
376 /opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/draft.rb:38:in
377 `default'
378 /opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/draft.rb:38:in `[]'
379 /opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/draft.rb:38:in
380 `discard'
381 /opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/util.rb:499:in `send'
382 /opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/util.rb:499:in
383 `method_missing'
384 /opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/modes/resume-mode.rb:36:in
385 `send_message'
386 /opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/mode.rb:49:in `send'
387 /opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/mode.rb:49:in
388 `handle_input'
389 /opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/buffer.rb:240:in
390 `handle_input'
391 /opt/local/lib/ruby/gems/1.8/gems/sup-999/bin/sup:189
392 /opt/local/bin/sup:16:in `load'
393 /opt/local/bin/sup:16
394
395
396
397 --- IOError from thread: load threads for thread-index-mode
398 IO Error occured at <except.c>:93 in xraise
399 Error occured in fs_store.c:293 - fsi_seek_i
400 seeking pos 162482: <Bad file descriptor>
401
402 /opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/index.rb:362:in `default'
403 /opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/index.rb:362:in `[]'
404 /opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/index.rb:362:in `build_message'
405 /opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/index.rb:263:in `each_id_by_date'
406 /opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/thread.rb:330:in `call'
407 /opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/thread.rb:330:in `load_n_threads'
408 /opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/index.rb:263:in `each_id_by_date'
409 /opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/index.rb:263:in `each'
410 /opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/index.rb:263:in `each_id_by_date'
411 /opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/thread.rb:326:in `load_n_threads'
412 /opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/modes/thread-index-mode.rb:499:in `__unprotected_load_n_threads'
413 (eval):12:in `load_n_threads'
414 /opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/modes/thread-index-mode.rb:483:in `load_n_threads_background'
415 /opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup.rb:85:in `reporting_thread'
416 /opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup.rb:83:in `initialize'
417 /opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup.rb:83:in `new'
418 /opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup.rb:83:in `reporting_thread'
419 /opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/modes/thread-index-mode.rb:482:in `load_n_threads_background'
420 /opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/modes/thread-index-mode.rb:552:in `__unprotected_load_threads'
421 (eval):12:in `load_threads'
422 /opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/modes/thread-index-mode.rb:87:in `reload'
423 /opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/mode.rb:49:in `send'
424 /opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/mode.rb:49:in `handle_input'
425 /opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/buffer.rb:240:in `handle_input'
426 /opt/local/lib/ruby/gems/1.8/gems/sup-999/bin/sup:189
427 /opt/local/bin/sup:16:in `load'
428 /opt/local/bin/sup:16
429
430 From wmorgan-sup@masanjin.net Wed Aug 6 14:23:59 2008
431 From: wmorgan-sup@masanjin.net (William Morgan)
432 Date: Wed, 06 Aug 2008 11:23:59 -0700
433 Subject: [sup-talk] two sup crashes
434 In-Reply-To: <1218031573-sup-325@tangerine.lanl.gov>
435 References: <1218031573-sup-325@tangerine.lanl.gov>
436 Message-ID: <1218046971-sup-1407@entry>
437
438 Reformatted excerpts from John Bent's message of 2008-08-06:
439 > I was sending an email and sup crashed. I restarted, resent the
440 > email, and then it crashed again right after I archived some emails,
441 > saved the index and tried to refresh my screen. Both errors are below
442 > and seem to be related.
443
444 Do the same actions work if you restart Sup?
445
446 These are both Ferret index corruption errors, which means I can either
447 debug Ferret, or rewrite Sup to not use it. (I've chosen the latter.)
448 --
449 William <wmorgan-sup at masanjin.net>
450
451 From johnbent@lanl.gov Thu Aug 7 09:33:12 2008
452 From: johnbent@lanl.gov (John Bent)
453 Date: Thu, 07 Aug 2008 07:33:12 -0600
454 Subject: [sup-talk] two sup crashes
455 In-Reply-To: <1218046971-sup-1407@entry>
456 References: <1218031573-sup-325@tangerine.lanl.gov> <1218046971-sup-1407@entry>
457 Message-ID: <1218115911-sup-8006@tangerine.lanl.gov>
458
459 Excerpts from William Morgan's message of Wed Aug 06 12:23:59 -0600 2008:
460 > Reformatted excerpts from John Bent's message of 2008-08-06:
461 > > I was sending an email and sup crashed. I restarted, resent the
462 > > email, and then it crashed again right after I archived some emails,
463 > > saved the index and tried to refresh my screen. Both errors are below
464 > > and seem to be related.
465 >
466 > Do the same actions work if you restart Sup?
467 >
468 Yeah it does.
469
470 > These are both Ferret index corruption errors, which means I can either
471 > debug Ferret, or rewrite Sup to not use it. (I've chosen the latter.)
472 >
473 Oh, that's a relief actually. I also sometimes get what I recognize as
474 Ferret errors and ignore them since I know you're moving away from it.
475 I just somehow didn't recognize these.
476
477 From marcus-sup@bar-coded.net Thu Aug 7 10:24:07 2008
478 From: marcus-sup@bar-coded.net (Marcus Williams)
479 Date: Thu, 07 Aug 2008 15:24:07 +0100
480 Subject: [sup-talk] ThreadSet question
481 Message-ID: <1218118769-sup-1369@tomsk>
482
483 Hi -
484
485 I'm trying to get a set of threads back from a search (messing with a
486 web interface to sup - will send a patch once its up and running if
487 anyone is interested) but I cant get it to sort the threads in date
488 order as it does in the sup console. As far as I can see it should
489 just do it but for some reason it doesnt.
490
491 If I'm calling load_n_threads directly what do I have to do to get the
492 threads in date order?
493
494 Thanks
495
496 Marcus
497
498 From wmorgan-sup@masanjin.net Thu Aug 7 11:18:10 2008
499 From: wmorgan-sup@masanjin.net (William Morgan)
500 Date: Thu, 07 Aug 2008 08:18:10 -0700
501 Subject: [sup-talk] two sup crashes
502 In-Reply-To: <1218115911-sup-8006@tangerine.lanl.gov>
503 References: <1218031573-sup-325@tangerine.lanl.gov> <1218046971-sup-1407@entry>
504 <1218115911-sup-8006@tangerine.lanl.gov>
505 Message-ID: <1218122247-sup-300@entry>
506
507 Reformatted excerpts from John Bent's message of 2008-08-07:
508 > Excerpts from William Morgan's message of Wed Aug 06 12:23:59 -0600 2008:
509 > > Do the same actions work if you restart Sup?
510 > >
511 > Yeah it does.
512
513 Then consider yourself lucky!
514
515 And do a sup-dump just in case.
516 --
517 William <wmorgan-sup at masanjin.net>
518
519 From wmorgan-sup@masanjin.net Thu Aug 7 11:24:11 2008
520 From: wmorgan-sup@masanjin.net (William Morgan)
521 Date: Thu, 07 Aug 2008 08:24:11 -0700
522 Subject: [sup-talk] ThreadSet question
523 In-Reply-To: <1218118769-sup-1369@tomsk>
524 References: <1218118769-sup-1369@tomsk>
525 Message-ID: <1218122471-sup-9206@entry>
526
527 Reformatted excerpts from Marcus Williams's message of 2008-08-07:
528 > I'm trying to get a set of threads back from a search (messing with a
529 > web interface to sup - will send a patch once its up and running if
530 > anyone is interested)
531
532 Cool!
533
534 > If I'm calling load_n_threads directly what do I have to do to get the
535 > threads in date order?
536
537 I explicitly sort them by date before display. See ThreadIndexMode#update.
538 Once they're loaded I pull them out of @ts.threads and into @threads,
539 and sort them.
540 --
541 William <wmorgan-sup at masanjin.net>
542
543 From marcus-sup@bar-coded.net Thu Aug 7 16:18:03 2008
544 From: marcus-sup@bar-coded.net (Marcus Williams)
545 Date: Thu, 07 Aug 2008 21:18:03 +0100
546 Subject: [sup-talk] ThreadSet question
547 In-Reply-To: <1218122471-sup-9206@entry>
548 References: <1218118769-sup-1369@tomsk> <1218122471-sup-9206@entry>
549 Message-ID: <1218140167-sup-3154@tomsk>
550
551 On 7.8.2008, William Morgan wrote:
552 > > If I'm calling load_n_threads directly what do I have to do to get the
553 > > threads in date order?
554 >
555 > I explicitly sort them by date before display. See ThreadIndexMode#update.
556 > Once they're loaded I pull them out of @ts.threads and into @threads,
557 > and sort them.
558
559 Ah, that explains it :) ... and now I have sorted threads. Bit more
560 work and this might actually be useful!
561
562 Marcus
563
564 From cj.fleck@gmail.com Fri Aug 8 09:38:47 2008
565 From: cj.fleck@gmail.com (CJ Fleck)
566 Date: Fri, 08 Aug 2008 09:38:47 -0400
567 Subject: [sup-talk] Crash when browsing search results
568 Message-ID: <1218202655-sup-110@archie>
569
570 I did a basic search over all messages, and as I moved the "cursor"
571 down so it would load unseen threads, it crashed. See attached...
572 -------------- next part --------------
573 An embedded and charset-unspecified text was scrubbed...
574 Name: sup-exception-log.txt
575 URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20080808/1bc1d5ed/attachment.txt>
576
577 From nicolas.pouillard@gmail.com Sun Aug 10 05:53:04 2008
578 From: nicolas.pouillard@gmail.com (Nicolas Pouillard)
579 Date: Sun, 10 Aug 2008 11:53:04 +0200
580 Subject: [sup-talk] Sup Backtrace While Polling
581 Message-ID: <cd67f63a0808100253i7d3703adt61ce1c83dad1ab80@mail.gmail.com>
582
583 Hi all,
584
585 Today sup stopped working for me. Indeed while sup is polling I get
586 the attached backtrace. I have no idea about the reason but suspect
587 that some email is ill formatted and I will try to find it by editing
588 my mbox.
589
590 To edit my mbox I would like to use mutt, however I don't know how to
591 go to newer emails, currently that's older first and I have a 950MB
592 mbox so don't want to scroll...
593
594 --
595 Nicolas Pouillard aka Ertai
596 -------------- next part --------------
597 An embedded and charset-unspecified text was scrubbed...
598 Name: exception-log.txt
599 URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20080810/7aba198c/attachment-0001.txt>
600
601 From wmorgan-sup@masanjin.net Sun Aug 10 14:31:17 2008
602 From: wmorgan-sup@masanjin.net (William Morgan)
603 Date: Sun, 10 Aug 2008 11:31:17 -0700
604 Subject: [sup-talk] Sup Backtrace While Polling
605 In-Reply-To: <cd67f63a0808100253i7d3703adt61ce1c83dad1ab80@mail.gmail.com>
606 References: <cd67f63a0808100253i7d3703adt61ce1c83dad1ab80@mail.gmail.com>
607 Message-ID: <1218393032-sup-3985@entry>
608
609 Reformatted excerpts from nicolas.pouillard's message of 2008-08-10:
610 > --- TypeError from thread: poll after loading inbox
611 > can't modify frozen string
612 > /opt/local/lib/ruby/gems/1.8/gems/rmail-0.17/lib/rmail/parser/multipart.rb:159:in `[]='
613
614 Try changing line 159 of multipart.rb to:
615 chunk = chunk[0..start]
616
617 RMail hasn't been updated since like Ruby 1.8.2.
618 --
619 William <wmorgan-sup at masanjin.net>
620
621 From nicolas.pouillard@gmail.com Sun Aug 10 15:43:09 2008
622 From: nicolas.pouillard@gmail.com (Nicolas Pouillard)
623 Date: Sun, 10 Aug 2008 21:43:09 +0200
624 Subject: [sup-talk] Sup Backtrace While Polling
625 In-Reply-To: <1218393032-sup-3985@entry>
626 References: <cd67f63a0808100253i7d3703adt61ce1c83dad1ab80@mail.gmail.com>
627 <1218393032-sup-3985@entry>
628 Message-ID: <1218397192-sup-4246@ausone.local>
629
630 Excerpts from William Morgan's message of Sun Aug 10 20:31:17 +0200 2008:
631 > Reformatted excerpts from nicolas.pouillard's message of 2008-08-10:
632 > > --- TypeError from thread: poll after loading inbox
633 > > can't modify frozen string
634 > > /opt/local/lib/ruby/gems/1.8/gems/rmail-0.17/lib/rmail/parser/multipart.rb:159:in `[]='
635 >
636 > Try changing line 159 of multipart.rb to:
637 > chunk = chunk[0..start]
638
639 Many thanks!!! I'm back to sup!
640
641 > RMail hasn't been updated since like Ruby 1.8.2.
642
643 That's sad. Is RMail active again?
644
645 Otherwise sup should really consider having a personal version of it.
646
647 BTW another question, how can I split my mbox file and sync sup again?
648
649 Cheers,
650
651 --
652 Nicolas Pouillard aka Ertai
653 -------------- next part --------------
654 A non-text attachment was scrubbed...
655 Name: signature.asc
656 Type: application/pgp-signature
657 Size: 194 bytes
658 Desc: not available
659 URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20080810/a7013445/attachment.bin>
660
661 From marcus-sup@bar-coded.net Sun Aug 10 16:36:00 2008
662 From: marcus-sup@bar-coded.net (Marcus Williams)
663 Date: Sun, 10 Aug 2008 21:36:00 +0100
664 Subject: [sup-talk] Sup Backtrace While Polling
665 In-Reply-To: <1218397192-sup-4246@ausone.local>
666 References: <cd67f63a0808100253i7d3703adt61ce1c83dad1ab80@mail.gmail.com>
667 <1218393032-sup-3985@entry> <1218397192-sup-4246@ausone.local>
668 Message-ID: <1218400279-sup-8057@tomsk>
669
670 On 10.8.2008, Nicolas Pouillard wrote:
671 > BTW another question, how can I split my mbox file and sync sup again?
672
673 Use ruby and rmail ;)
674
675 ... actually I'm not joking I just split a 600mb mbox with rmail into
676 month-year archives and it worked really well. Use the
677 RMail::Mailbox.parse_mbox method to parse you file into raw messages
678 and then you can use RMail::Parser.read(raw).header.date to give you
679 something you can turn into a date/month string.
680
681 Use sup-dump before you split, and then restore from that after you
682 set up all the mboxes as your new sources with sup-add.
683
684 HTH
685
686 Marcus
687
688 From alec@thened.net Sun Aug 10 19:53:52 2008
689 From: alec@thened.net (Alec Berryman)
690 Date: Sun, 10 Aug 2008 19:53:52 -0400
691 Subject: [sup-talk] Initial import does not preserve read/unread status
692 Message-ID: <20080810235352.GA20706@thened.net>
693
694 The new user guide says about sup-add:
695
696 "You can also specify --read to mark all imported messages as read; the
697 default is to preserve the read/unread status from the source."
698
699 When I imported a new maildir source with a mix of read and unread
700 messages (in the cur or new subfolder, respectively), all of the
701 messages were marked unread. Is the documentation wrong or is this a
702 bug? I hope it's a bug.
703
704 From alec@thened.net Sun Aug 10 20:13:24 2008
705 From: alec@thened.net (Alec Berryman)
706 Date: Sun, 10 Aug 2008 20:13:24 -0400
707 Subject: [sup-talk] Initial import does not preserve read/unread status
708 In-Reply-To: <20080810235352.GA20706@thened.net>
709 References: <20080810235352.GA20706@thened.net>
710 Message-ID: <20080811001324.GA24661@thened.net>
711
712 Alec Berryman on 2008-08-10 19:53:52 -0400:
713
714 > The new user guide says about sup-add:
715 >
716 > "You can also specify --read to mark all imported messages as read; the
717 > default is to preserve the read/unread status from the source."
718 >
719 > When I imported a new maildir source with a mix of read and unread
720 > messages (in the cur or new subfolder, respectively), all of the
721 > messages were marked unread. Is the documentation wrong or is this a
722 > bug? I hope it's a bug.
723
724 On second thought, that was a horrible bug report.
725
726 I'm using sup-0.6 from gems. I haven't done anything fancy; I just ran
727 'gem install sup', and it appears all my gem packages are up to date. I
728 configured sup by running sup-config, entering my name and address,
729 taking the other defaults, and then not adding any sources. I added one
730 source later using `sup-add maildir:/path/to/maildir'. Mutt and manual
731 inspection of the maildir shows most of the messages being read, but sup
732 shows all of them unread. The behavior does not change if I remove
733 ~/.sup and run the same sequence of commands except for adding a
734 sup-sync between running sup-add and sup.
735
736 From wmorgan-sup@masanjin.net Tue Aug 12 23:14:09 2008
737 From: wmorgan-sup@masanjin.net (William Morgan)
738 Date: Tue, 12 Aug 2008 20:14:09 -0700
739 Subject: [sup-talk] Initial import does not preserve read/unread status
740 In-Reply-To: <20080810235352.GA20706@thened.net>
741 References: <20080810235352.GA20706@thened.net>
742 Message-ID: <1218597196-sup-3699@entry>
743
744 Reformatted excerpts from Alec Berryman's message of 2008-08-10:
745 > When I imported a new maildir source with a mix of read and unread
746 > messages (in the cur or new subfolder, respectively), all of the
747 > messages were marked unread. Is the documentation wrong or is this a
748 > bug? I hope it's a bug.
749
750 Weird. Can you provide some sample filenames for read and unread
751 messages? (Since that's how Maildir keeps state---it might be there's
752 some naming variant that Sup doesn't know about.)
753 --
754 William <wmorgan-sup at masanjin.net>
755
756 From wmorgan-sup@masanjin.net Tue Aug 12 23:15:51 2008
757 From: wmorgan-sup@masanjin.net (William Morgan)
758 Date: Tue, 12 Aug 2008 20:15:51 -0700
759 Subject: [sup-talk] Sup Backtrace While Polling
760 In-Reply-To: <1218400279-sup-8057@tomsk>
761 References: <cd67f63a0808100253i7d3703adt61ce1c83dad1ab80@mail.gmail.com>
762 <1218393032-sup-3985@entry> <1218397192-sup-4246@ausone.local>
763 <1218400279-sup-8057@tomsk>
764 Message-ID: <1218597311-sup-7061@entry>
765
766 Reformatted excerpts from Marcus Williams's message of 2008-08-10:
767 > On 10.8.2008, Nicolas Pouillard wrote:
768 > > BTW another question, how can I split my mbox file and sync sup
769 > > again?
770 >
771 > Use ruby and rmail ;)
772 [snip]
773 > Use sup-dump before you split, and then restore from that after you
774 > set up all the mboxes as your new sources with sup-add.
775
776 Yep, this is pretty much what I would recommend too.
777 --
778 William <wmorgan-sup at masanjin.net>
779
780 From wmorgan-sup@masanjin.net Tue Aug 12 23:22:41 2008
781 From: wmorgan-sup@masanjin.net (William Morgan)
782 Date: Tue, 12 Aug 2008 20:22:41 -0700
783 Subject: [sup-talk] safe index in the after-poll.rb ?
784 In-Reply-To: <1218025176-sup-6853@daniel-laptop>
785 References: <1218025176-sup-6853@daniel-laptop>
786 Message-ID: <1218597645-sup-7784@entry>
787
788 Reformatted excerpts from Daniel Neubacher's message of 2008-08-06:
789 > This is working, but only when the index is safed. When i read some
790 > mails and do not safe the index the count doesnt give me the right
791 > amount of unread mails back. So is there a way to save the index
792 > automaticly after polling my mails ?
793
794 Let's see... this is untested, but in your after-poll hook you
795 could try something like:
796
797 BufferManager.buffers.each { |name, b| b.save if b.is_a? ThreadIndexMode }
798 --
799 William <wmorgan-sup at masanjin.net>
800
801 From alec@thened.net Sun Aug 17 14:59:15 2008
802 From: alec@thened.net (Alec Berryman)
803 Date: Sun, 17 Aug 2008 14:59:15 -0400
804 Subject: [sup-talk] Initial import does not preserve read/unread status
805 In-Reply-To: <1218597196-sup-3699@entry>
806 References: <20080810235352.GA20706@thened.net> <1218597196-sup-3699@entry>
807 Message-ID: <20080817185915.GA17717@thened.net>
808
809 William Morgan on 2008-08-12 20:14:09 -0700:
810
811 > Reformatted excerpts from Alec Berryman's message of 2008-08-10:
812 > > When I imported a new maildir source with a mix of read and unread
813 > > messages (in the cur or new subfolder, respectively), all of the
814 > > messages were marked unread. Is the documentation wrong or is this a
815 > > bug? I hope it's a bug.
816 >
817 > Weird. Can you provide some sample filenames for read and unread
818 > messages? (Since that's how Maildir keeps state---it might be there's
819 > some naming variant that Sup doesn't know about.)
820
821 Sure (ls -R output; maildir attached; samples from sup-talk):
822
823 sup-does-not-import-read-messages-as-read/:
824 cur/
825 new/
826 tmp/
827
828 sup-does-not-import-read-messages-as-read/cur:
829 1218394528_0.8381.barry,U=23205,FMD5=d25c71bb54a5e1f674c1d0df91b0b4fe:2,S
830 1218397749_0.16026.barry,U=23207,FMD5=d25c71bb54a5e1f674c1d0df91b0b4fe:2,S
831 1218405160_1.1978.barry,U=23211,FMD5=d25c71bb54a5e1f674c1d0df91b0b4fe:2,S
832 1218413059_0.23982.barry,U=23215,FMD5=d25c71bb54a5e1f674c1d0df91b0b4fe:2,RS
833 1218413717_1.26111.barry,U=23216,FMD5=d25c71bb54a5e1f674c1d0df91b0b4fe:2,S
834 1218626652_4.3870.barry,U=23368,FMD5=d25c71bb54a5e1f674c1d0df91b0b4fe:2,S
835 1218626652_5.3870.barry,U=23369,FMD5=d25c71bb54a5e1f674c1d0df91b0b4fe:2,S
836
837 sup-does-not-import-read-messages-as-read/new:
838 1218626652_2.3870.barry,U=23366,FMD5=d25c71bb54a5e1f674c1d0df91b0b4fe
839
840 sup-does-not-import-read-messages-as-read/tmp:
841
842
843 When I import this folder with sup, I see all messages marked as new,
844 but I only expect to see 1. The maildir names are generated by
845 offlineimap.
846 -------------- next part --------------
847 A non-text attachment was scrubbed...
848 Name: sup-does-not-import-read-messages-as-read.tar.bz2
849 Type: application/octet-stream
850 Size: 6635 bytes
851 Desc: not available
852 URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20080817/485a2391/attachment-0001.obj>
853
854 From manish@gslab.com Tue Aug 19 08:13:02 2008
855 From: manish@gslab.com (Manish Sapariya)
856 Date: Tue, 19 Aug 2008 17:43:02 +0530
857 Subject: [sup-talk] fetching imap sub folder
858 Message-ID: <48AAB8CE.9060701@gslab.com>
859
860 Hi,
861 I want to fetch one subfolder on my IMAP server. Thunderbird
862 has following hierarchy
863
864 INBOX
865 ->mail
866 ->supmails (This folder have the mails that I want to fetch
867 using sup.)
868
869
870 I tried following combinations for specifying the source
871
872 imaps://padma.gslab.com/Inbox/mail/supsource/
873 imaps://padma.gslab.com/Inbox/mail/supsource
874 imaps://padma.gslab.com//Inbox//mail//supsource
875
876 none worked as expected and sup reports.
877
878 ~
879 Source: imaps://padma.gslab.com/Inbox/mail/supsource/
880 Error: While communicating with IMAP server (type
881 Net::IMAP::NoResponseError): "Mailbox does not exist, or must be
882 subscribed to."
883 ~
884
885 Any ideas?
886
887 By the way, when I was running this with my existing sup configuration,
888 I could not figure out and there was no indication. When I created new
889 sup directory and specified this source as the only source I could get
890 this error message. I looked into the log but I could not see the error.
891 Did I missed anything?
892
893 Thanks and Regards,
894 Manish
895
896 From steve@patter.mine.nu Tue Aug 19 09:03:05 2008
897 From: steve@patter.mine.nu (Stephen Patterson)
898 Date: Tue, 19 Aug 2008 14:03:05 +0100
899 Subject: [sup-talk] fetching imap sub folder
900 In-Reply-To: <48AAB8CE.9060701@gslab.com>
901 References: <48AAB8CE.9060701@gslab.com>
902 Message-ID: <20080819130304.GA15109@patter.mine.nu>
903
904 On 19 Aug 08, Manish Sapariya (manish at gslab.com) wrote:
905 > Hi,
906 > I want to fetch one subfolder on my IMAP server. Thunderbird
907 > has following hierarchy
908
909 > I tried following combinations for specifying the source
910 >
911 > imaps://padma.gslab.com/Inbox/mail/supsource/
912 > imaps://padma.gslab.com/Inbox/mail/supsource
913 > imaps://padma.gslab.com//Inbox//mail//supsource
914
915 try the following (the syntax I use with a Dovecot IMAP server).
916 imaps://padma.gslab.com/Inbox.mail.supsource
917
918
919 --
920 Stephen Patterson :: steve at patter.me.uk :: http://patter.mine.nu/
921 GPG: B416F0DE :: Jabber: patter at jabber.earth.li
922 "Don't be silly, Minnie. Who'd be walking round these cliffs with a gas oven?"
923 -------------- next part --------------
924 A non-text attachment was scrubbed...
925 Name: not available
926 Type: application/pgp-signature
927 Size: 197 bytes
928 Desc: Digital signature
929 URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20080819/4e94aff6/attachment.bin>
930
931 From manish@gslab.com Tue Aug 19 09:19:21 2008
932 From: manish@gslab.com (Manish Sapariya)
933 Date: Tue, 19 Aug 2008 18:49:21 +0530
934 Subject: [sup-talk] fetching imap sub folder
935 In-Reply-To: <20080819130304.GA15109@patter.mine.nu>
936 References: <48AAB8CE.9060701@gslab.com>
937 <20080819130304.GA15109@patter.mine.nu>
938 Message-ID: <48AAC859.1040709@gslab.com>
939
940 Thanks,
941 that was it.
942 :-)
943 Manish
944
945 Stephen Patterson wrote:
946 > On 19 Aug 08, Manish Sapariya (manish at gslab.com) wrote:
947 >> Hi,
948 >> I want to fetch one subfolder on my IMAP server. Thunderbird
949 >> has following hierarchy
950 >
951 >> I tried following combinations for specifying the source
952 >>
953 >> imaps://padma.gslab.com/Inbox/mail/supsource/
954 >> imaps://padma.gslab.com/Inbox/mail/supsource
955 >> imaps://padma.gslab.com//Inbox//mail//supsource
956 >
957 > try the following (the syntax I use with a Dovecot IMAP server).
958 > imaps://padma.gslab.com/Inbox.mail.supsource
959 >
960 >
961 >
962 >
963 > ------------------------------------------------------------------------
964 >
965 > _______________________________________________
966 > sup-talk mailing list
967 > sup-talk at rubyforge.org
968 > http://rubyforge.org/mailman/listinfo/sup-talk
969
970 From bdwalton@gmail.com Fri Aug 22 18:23:02 2008
971 From: bdwalton@gmail.com (Ben Walton)
972 Date: Fri, 22 Aug 2008 18:23:02 -0400
973 Subject: [sup-talk] split threads?
974 Message-ID: <f96e0240808221523k7b273a78p969e5e3029abb57d@mail.gmail.com>
975
976 Hi All,
977
978 I was wondering what other people think about an option to split
979 threads apart (in a similar way to how they can be joined). A use
980 case: people that find an old email to a certain address and use it to
981 compose a reply (after clearing the subject). This sees a (decent)
982 mail client insert the References and In-Reply-To headers, etc from
983 the original thread. Sup happily uses these to insert this new
984 message/thread into an old one.
985
986 Do others run into this too?
987
988 Thanks
989 -Ben
990 --
991 ---------------------------------------------------------------------------------------------------------------------------
992 Ben Walton <bdwalton at gmail.com>
993
994 When one person suffers from a delusion, it is called insanity. When
995 many people suffer from a delusion it is called Religion.
996 Robert M. Pirsig, Zen and the Art of Motorcycle Maintenance
997
998 ---------------------------------------------------------------------------------------------------------------------------
999
1000 From barton.schaefer@gmail.com Sat Aug 23 19:15:12 2008
1001 From: barton.schaefer@gmail.com (Bart Schaefer)
1002 Date: Sat, 23 Aug 2008 16:15:12 -0700
1003 Subject: [sup-talk] Some comments on sup-0.6
1004 Message-ID: <6bb609560808231615o1b7dc71eh48d192375e46cf8c@mail.gmail.com>
1005
1006 "The goal of Sup is to become the email client of choice for nerds everywhere."
1007
1008 I encountered sup a few days ago via a link on Justin Mason's blog,
1009 and it sounded interesting enough to try it out. There are quite a
1010 few things about it that I like, but there are a few things about it
1011 that currently are just plain show-stoppers. None of them is
1012 irreparable, but IMO taken together they almost disqualify it from
1013 being called an "email client" at this time.
1014
1015 First the good stuff: I entirely approve of the choices of ideas to
1016 borrow from gmail, and the addition of being able to mark and coalesce
1017 threads is something I wish gmail would borrow back. The key bindings
1018 weren't too hard to figure out (and probably would have been easier if
1019 I'd used mutt more in the past). The expanding/collapsing views of
1020 threads and quoted messages work nicely most of the time. I could
1021 immediately see how sup could help me clean up the mess some of my
1022 mail stores have become, to find and conceal old stuff without
1023 completely losing track of it and prioritize important stuff. Great
1024 work.
1025
1026 (At the same time, that last is what seems to be lacking in
1027 follow-through. See below.)
1028
1029 One suggestion for an improvement on the gmail interface: Consider
1030 introducing a hierarchy syntax in labels. E.g., if I've got a label
1031 for "restaurants" I might create a label "restaurants/lunch" that
1032 means "first search for anything tagged restaraurants and then narrow
1033 by searching for anything also tagged lunch". In any UI that shows a
1034 list of the labels, collapse the heirarchy so that I don't have to see
1035 both "restaurants" and "restaurants/lunch" at the same time. This
1036 creates an interface familiar to users who are accustomed to having
1037 folders arranged hierarchically, without changing the search model
1038 that ultimately locates the referenced messages.
1039
1040 (Is it possible to search for messages based on which source they came from?)
1041
1042 Next some nits or minor problems, in no particular order ...
1043
1044 The default color scheme is pretty terrible. (I did mention there'd be "nits".)
1045
1046 When I widened my terminal window to try to see more of the preview
1047 text on the thread screen, sup didn't pick up on the size change.
1048
1049 There's either no on-screen help for how one builds up a search
1050 expression, or it's simply too hard to find that help, and in
1051 particular it wasn't obvious how one searches for all messages having
1052 a certain label (I was expecting maybe something like gmail's
1053 label:Xyz syntax).
1054
1055 It should be possible to create search that matches a label without
1056 finding other messages that happen to contain the same word (maybe it
1057 is possible and I just haven't figure out how yet).
1058
1059 I happened to encounter a case of new mail arriving while I was using
1060 sup, wherein a colleague had replied to a message by editing the
1061 Subject such that his entire reply was there and the message body was
1062 empty. Sup collapsed this into the thread and hid his new subject
1063 behind the original subject. I had to bail out and switch over to
1064 alpine to figure out why he'd sent a seemingly empty message.
1065
1066 OK, now the show stoppers.
1067
1068 I have a LOT of IMAP folders (conservatively, hundreds), many of them
1069 in a shared hierarchy not under my control; sup's interface would be
1070 the perfect way to get a handle on these, but it would take me way too
1071 long to add them one by one as separate URL sources. At the moment
1072 sup might be described as phenomenal cosmic power in an itty-bitty
1073 living space.
1074
1075 If you're going to have any hope of becoming the choice of nerds
1076 everywhere, you've got address the "play well with others" problem, at
1077 the very least with the IMAP INBOX, if not with other mailboxes.
1078 Forcing me to exit from sup and do a complete re-index whenever a
1079 message disappears is just not going to fly, particularly for a
1080 protocol that provides so many tools for keeping in sync. I know,
1081 this doesn't fit with the "never delete anything, just stop looking at
1082 it" model that sup wants to present, but in the real world even nerds
1083 can't store things in their inbox forever, and for it to really be THE
1084 email client of choice, I want to keep sup running for weeks at a time
1085 and never have a reason to leave the interface (except maybe to escape
1086 to a web browser or to drop into my editor when composing mail).
1087
1088 By the same token, sup needs to be able to push deletion marks back up
1089 to the IMAP server and purge the mailbox. Even if you violate the
1090 IMAP usage model by implementing delete as some kind of move-to-trash
1091 operation, so that sup can keep indexing the trash, there has to be a
1092 way for the user to manage the size of his inbox without switching to
1093 some other means of accessing the server. And to really take
1094 advantage of sup's ability to search and classify to clean up my messy
1095 mail store, I need a way to permanently throw away all the spam and
1096 duplicate messages that have accumulated in the odd procmail-created
1097 corners of my folder space. It's even fine if the only way to do this
1098 is through IMAP or the like; sup does not need to incorporate the
1099 mechanics of local mailbox management.
1100
1101 That's about it for impressions from a few hours of experimentation.
1102 I think sup shows great promise and I've joined the mailing list to
1103 keep track of its progress. Congratulations on what you've got so
1104 far, and I look forward to seeing more.
1105
1106 From luis@tieguy.org Sat Aug 23 19:20:22 2008
1107 From: luis@tieguy.org (Luis Villa)
1108 Date: Sat, 23 Aug 2008 19:20:22 -0400
1109 Subject: [sup-talk] Some comments on sup-0.6
1110 In-Reply-To: <6bb609560808231615o1b7dc71eh48d192375e46cf8c@mail.gmail.com>
1111 References: <6bb609560808231615o1b7dc71eh48d192375e46cf8c@mail.gmail.com>
1112 Message-ID: <2cb10c440808231620k57396f1bw8547db09dded6abf@mail.gmail.com>
1113
1114 Possibly of interest, Bart:
1115 http://all-thing.net/2008/06/rethinking-sup.html
1116 http://all-thing.net/2008/07/rethinking-sup-part-ii.html
1117
1118 Luis (who isn't actually using sup, for many of the reasons you
1119 listed, but remains a fascinated lurker)
1120
1121 On Sat, Aug 23, 2008 at 7:15 PM, Bart Schaefer
1122 <barton.schaefer at gmail.com> wrote:
1123 > "The goal of Sup is to become the email client of choice for nerds everywhere."
1124 >
1125 > I encountered sup a few days ago via a link on Justin Mason's blog,
1126 > and it sounded interesting enough to try it out. There are quite a
1127 > few things about it that I like, but there are a few things about it
1128 > that currently are just plain show-stoppers. None of them is
1129 > irreparable, but IMO taken together they almost disqualify it from
1130 > being called an "email client" at this time.
1131 >
1132 > First the good stuff: I entirely approve of the choices of ideas to
1133 > borrow from gmail, and the addition of being able to mark and coalesce
1134 > threads is something I wish gmail would borrow back. The key bindings
1135 > weren't too hard to figure out (and probably would have been easier if
1136 > I'd used mutt more in the past). The expanding/collapsing views of
1137 > threads and quoted messages work nicely most of the time. I could
1138 > immediately see how sup could help me clean up the mess some of my
1139 > mail stores have become, to find and conceal old stuff without
1140 > completely losing track of it and prioritize important stuff. Great
1141 > work.
1142 >
1143 > (At the same time, that last is what seems to be lacking in
1144 > follow-through. See below.)
1145 >
1146 > One suggestion for an improvement on the gmail interface: Consider
1147 > introducing a hierarchy syntax in labels. E.g., if I've got a label
1148 > for "restaurants" I might create a label "restaurants/lunch" that
1149 > means "first search for anything tagged restaraurants and then narrow
1150 > by searching for anything also tagged lunch". In any UI that shows a
1151 > list of the labels, collapse the heirarchy so that I don't have to see
1152 > both "restaurants" and "restaurants/lunch" at the same time. This
1153 > creates an interface familiar to users who are accustomed to having
1154 > folders arranged hierarchically, without changing the search model
1155 > that ultimately locates the referenced messages.
1156 >
1157 > (Is it possible to search for messages based on which source they came from?)
1158 >
1159 > Next some nits or minor problems, in no particular order ...
1160 >
1161 > The default color scheme is pretty terrible. (I did mention there'd be "nits".)
1162 >
1163 > When I widened my terminal window to try to see more of the preview
1164 > text on the thread screen, sup didn't pick up on the size change.
1165 >
1166 > There's either no on-screen help for how one builds up a search
1167 > expression, or it's simply too hard to find that help, and in
1168 > particular it wasn't obvious how one searches for all messages having
1169 > a certain label (I was expecting maybe something like gmail's
1170 > label:Xyz syntax).
1171 >
1172 > It should be possible to create search that matches a label without
1173 > finding other messages that happen to contain the same word (maybe it
1174 > is possible and I just haven't figure out how yet).
1175 >
1176 > I happened to encounter a case of new mail arriving while I was using
1177 > sup, wherein a colleague had replied to a message by editing the
1178 > Subject such that his entire reply was there and the message body was
1179 > empty. Sup collapsed this into the thread and hid his new subject
1180 > behind the original subject. I had to bail out and switch over to
1181 > alpine to figure out why he'd sent a seemingly empty message.
1182 >
1183 > OK, now the show stoppers.
1184 >
1185 > I have a LOT of IMAP folders (conservatively, hundreds), many of them
1186 > in a shared hierarchy not under my control; sup's interface would be
1187 > the perfect way to get a handle on these, but it would take me way too
1188 > long to add them one by one as separate URL sources. At the moment
1189 > sup might be described as phenomenal cosmic power in an itty-bitty
1190 > living space.
1191 >
1192 > If you're going to have any hope of becoming the choice of nerds
1193 > everywhere, you've got address the "play well with others" problem, at
1194 > the very least with the IMAP INBOX, if not with other mailboxes.
1195 > Forcing me to exit from sup and do a complete re-index whenever a
1196 > message disappears is just not going to fly, particularly for a
1197 > protocol that provides so many tools for keeping in sync. I know,
1198 > this doesn't fit with the "never delete anything, just stop looking at
1199 > it" model that sup wants to present, but in the real world even nerds
1200 > can't store things in their inbox forever, and for it to really be THE
1201 > email client of choice, I want to keep sup running for weeks at a time
1202 > and never have a reason to leave the interface (except maybe to escape
1203 > to a web browser or to drop into my editor when composing mail).
1204 >
1205 > By the same token, sup needs to be able to push deletion marks back up
1206 > to the IMAP server and purge the mailbox. Even if you violate the
1207 > IMAP usage model by implementing delete as some kind of move-to-trash
1208 > operation, so that sup can keep indexing the trash, there has to be a
1209 > way for the user to manage the size of his inbox without switching to
1210 > some other means of accessing the server. And to really take
1211 > advantage of sup's ability to search and classify to clean up my messy
1212 > mail store, I need a way to permanently throw away all the spam and
1213 > duplicate messages that have accumulated in the odd procmail-created
1214 > corners of my folder space. It's even fine if the only way to do this
1215 > is through IMAP or the like; sup does not need to incorporate the
1216 > mechanics of local mailbox management.
1217 >
1218 > That's about it for impressions from a few hours of experimentation.
1219 > I think sup shows great promise and I've joined the mailing list to
1220 > keep track of its progress. Congratulations on what you've got so
1221 > far, and I look forward to seeing more.
1222 > _______________________________________________
1223 > sup-talk mailing list
1224 > sup-talk at rubyforge.org
1225 > http://rubyforge.org/mailman/listinfo/sup-talk
1226 >
1227
1228 From barton.schaefer@gmail.com Sat Aug 23 19:57:37 2008
1229 From: barton.schaefer@gmail.com (Bart Schaefer)
1230 Date: Sat, 23 Aug 2008 16:57:37 -0700
1231 Subject: [sup-talk] Some comments on sup-0.6
1232 In-Reply-To: <2cb10c440808231620k57396f1bw8547db09dded6abf@mail.gmail.com>
1233 References: <6bb609560808231615o1b7dc71eh48d192375e46cf8c@mail.gmail.com>
1234 <2cb10c440808231620k57396f1bw8547db09dded6abf@mail.gmail.com>
1235 Message-ID: <6bb609560808231657m27ec05fq3418cc9ad5f4eb27@mail.gmail.com>
1236
1237 On Sat, Aug 23, 2008 at 4:20 PM, Luis Villa <luis at tieguy.org> wrote:
1238 > Possibly of interest, Bart:
1239 > http://all-thing.net/2008/06/rethinking-sup.html
1240 > http://all-thing.net/2008/07/rethinking-sup-part-ii.html
1241
1242 That is of interest, thanks. Doesn't actually invalidate very much of
1243 what I said, though. :-)
1244
1245 Those blog posts are from a couple of months ago. I could go comment
1246 there, or I could comment here. Any preference?
1247
1248 From wmorgan-sup@masanjin.net Sun Aug 24 20:01:51 2008
1249 From: wmorgan-sup@masanjin.net (William Morgan)
1250 Date: Sun, 24 Aug 2008 17:01:51 -0700
1251 Subject: [sup-talk] Some comments on sup-0.6
1252 In-Reply-To: <6bb609560808231657m27ec05fq3418cc9ad5f4eb27@mail.gmail.com>
1253 References: <6bb609560808231615o1b7dc71eh48d192375e46cf8c@mail.gmail.com>
1254 <2cb10c440808231620k57396f1bw8547db09dded6abf@mail.gmail.com>
1255 <6bb609560808231657m27ec05fq3418cc9ad5f4eb27@mail.gmail.com>
1256 Message-ID: <1219622436-sup-327@entry>
1257
1258 Reformatted excerpts from barton.schaefer's message of 2008-08-23:
1259 > Those blog posts are from a couple of months ago. I could go comment
1260 > there, or I could comment here. Any preference?
1261
1262 Here's probably better for anything substantial. Non-threaded blog
1263 comments are about as crappy a discussion medium as I can imagine.
1264 --
1265 William <wmorgan-sup at masanjin.net>
1266
1267 From wmorgan-sup@masanjin.net Sun Aug 24 20:30:30 2008
1268 From: wmorgan-sup@masanjin.net (William Morgan)
1269 Date: Sun, 24 Aug 2008 17:30:30 -0700
1270 Subject: [sup-talk] Some comments on sup-0.6
1271 In-Reply-To: <6bb609560808231615o1b7dc71eh48d192375e46cf8c@mail.gmail.com>
1272 References: <6bb609560808231615o1b7dc71eh48d192375e46cf8c@mail.gmail.com>
1273 Message-ID: <1219622542-sup-6624@entry>
1274
1275 Hi Barton,
1276
1277 Thanks for all the comments! Many of the issues you bring up are real.
1278 My current focus is on the backend to Sup 2.0, but in general I'm happy
1279 to accept patches and merge requests to fix these issues.
1280
1281 Detailed comments inlined:
1282
1283 Reformatted excerpts from barton.schaefer's message of 2008-08-23:
1284 > One suggestion for an improvement on the gmail interface: Consider
1285 > introducing a hierarchy syntax in labels. E.g., if I've got a label
1286 > for "restaurants" I might create a label "restaurants/lunch" that
1287 > means "first search for anything tagged restaraurants and then narrow
1288 > by searching for anything also tagged lunch".
1289
1290 Personally I don't like the idea of adding structure to labels, because
1291 this proposal (and others before it) are oriented at people with a lot
1292 of labels, and I suspect that too many labels is a symptom that you're
1293 doing something wrong.
1294
1295 That said, I know I'm crazy, and I would accept a patch that made this
1296 an (optional!) feature. One easy way might be to make it solely a UI
1297 tweak to LabelSearchMode, where any labels with a "/" in them are fit
1298 into a pre-collapsed hierarchy instead of displayed in a big list.
1299
1300 > (Is it possible to search for messages based on which source they came
1301 > from?)
1302
1303 Technically yes, but there's not a good interface on top of it. Search
1304 for "source_id:X", where X is the numeric source id of the source, which
1305 you have look up in sources.yaml.
1306
1307 > The default color scheme is pretty terrible. (I did mention there'd
1308 > be "nits".)
1309
1310 I like it, but maybe I'm just accustomed to it. It's configurable, and
1311 I'd accept patches for the default, if, say, more than one other person
1312 felt was better.
1313
1314 > When I widened my terminal window to try to see more of the preview
1315 > text on the thread screen, sup didn't pick up on the size change.
1316
1317 I could never get SIGWINCH to work due to a weird interaction between
1318 curses and Ruby threads. If you can, I'd be happy to accept a patch.
1319 In the meantime, you can press ^L to redraw the screen, and Sup should
1320 notice the change.
1321
1322 > There's either no on-screen help for how one builds up a search
1323 > expression, or it's simply too hard to find that help, and in
1324 > particular it wasn't obvious how one searches for all messages having
1325 > a certain label (I was expecting maybe something like gmail's
1326 > label:Xyz syntax).
1327
1328 The "label:asdf" syntax should work as you expect.
1329
1330 I agree that better search expression help would be nice. Patches
1331 accepted. :)
1332
1333 > I happened to encounter a case of new mail arriving while I was using
1334 > sup, wherein a colleague had replied to a message by editing the
1335 > Subject such that his entire reply was there and the message body was
1336 > empty. Sup collapsed this into the thread and hid his new subject
1337 > behind the original subject. I had to bail out and switch over to
1338 > alpine to figure out why he'd sent a seemingly empty message.
1339
1340 I think that if you had expanded the header (with 'h') while in
1341 thread-view-mode, you would've seen the full subject.
1342
1343 > I have a LOT of IMAP folders (conservatively, hundreds), many of them
1344 > in a shared hierarchy not under my control; sup's interface would be
1345 > the perfect way to get a handle on these, but it would take me way too
1346 > long to add them one by one as separate URL sources.
1347
1348 Agreed. This has been on the todo list for a while.
1349
1350 > If you're going to have any hope of becoming the choice of nerds
1351 > everywhere, you've got address the "play well with others" problem, at
1352 > the very least with the IMAP INBOX, if not with other mailboxes.
1353
1354 Actually, I'm going to be taking a very different tack in Sup 2.0, and
1355 not deal with IMAP at all. Sup will maintain its own document store, and
1356 it's going to be up to the user to insert your mail into it.
1357
1358 I know that's probably not the answer you want. But I have no desire to
1359 spend the requisite years of my life dealing with with hokey IMAP
1360 servers, Ruby's hokey IMAP libraries, and everything in between. I've
1361 taken a few steps down that path, but that's been more than enough to
1362 recognize it as the path to madness.
1363
1364 --
1365 William <wmorgan-sup at masanjin.net>
1366
1367 From wmorgan-sup@masanjin.net Sun Aug 24 20:38:30 2008
1368 From: wmorgan-sup@masanjin.net (William Morgan)
1369 Date: Sun, 24 Aug 2008 17:38:30 -0700
1370 Subject: [sup-talk] split threads?
1371 In-Reply-To: <f96e0240808221523k7b273a78p969e5e3029abb57d@mail.gmail.com>
1372 References: <f96e0240808221523k7b273a78p969e5e3029abb57d@mail.gmail.com>
1373 Message-ID: <1219624661-sup-6433@entry>
1374
1375 Reformatted excerpts from Ben Walton's message of 2008-08-22:
1376 > Do others run into this too?
1377
1378 All the time! I'd love to have this. I'd also love to figure out why
1379 thread joining doesn't work, half the time.
1380 --
1381 William <wmorgan-sup at masanjin.net>
1382
1383 From barton.schaefer@gmail.com Mon Aug 25 12:39:14 2008
1384 From: barton.schaefer@gmail.com (Bart Schaefer)
1385 Date: Mon, 25 Aug 2008 09:39:14 -0700
1386 Subject: [sup-talk] Some comments on sup-0.6
1387 In-Reply-To: <1219622542-sup-6624@entry>
1388 References: <6bb609560808231615o1b7dc71eh48d192375e46cf8c@mail.gmail.com>
1389 <1219622542-sup-6624@entry>
1390 Message-ID: <6bb609560808250939u6e8d4d16ycaf25c2ad1ea9fc7@mail.gmail.com>
1391
1392 On Sun, Aug 24, 2008 at 5:30 PM, William Morgan
1393 <wmorgan-sup at masanjin.net> wrote:
1394 > Hi Barton,
1395
1396 "Bart" is fine. I only display it the "long way" to stop people from
1397 calling me "Bartholomew."
1398
1399 > My current focus is on the backend to Sup 2.0, but in general I'm happy
1400 > to accept patches and merge requests to fix these issues.
1401
1402 Unfortunately I'm not much of a ruby programmer yet. Practically
1403 anything else for longer than I want to think about, but not ruby,
1404 though I'm looking at it.
1405
1406 > Personally I don't like the idea of adding structure to labels, because
1407 > this proposal (and others before it) are oriented at people with a lot
1408 > of labels, and I suspect that too many labels is a symptom that you're
1409 > doing something wrong.
1410
1411 It's an organizational thing. Some people think better in hierarchy.
1412 And occasionally one has as a message that relates closely to a
1413 particular subject but doesn't mention any of the usual terms one
1414 would search for, so it's handy to have a way to force a connection.
1415
1416 > That said, I know I'm crazy, and I would accept a patch that made this
1417 > an (optional!) feature. One easy way might be to make it solely a UI
1418 > tweak to LabelSearchMode, where any labels with a "/" in them are fit
1419 > into a pre-collapsed hierarchy instead of displayed in a big list.
1420
1421 That's essentially what I was suggesting.
1422
1423 > I agree that better search expression help would be nice. Patches
1424 > accepted. :)
1425
1426 Does anyone other than you really know what the help should say?
1427
1428 >> If you're going to have any hope of becoming the choice of nerds
1429 >> everywhere, you've got address the "play well with others" problem, at
1430 >> the very least with the IMAP INBOX, if not with other mailboxes.
1431 >
1432 > Actually, I'm going to be taking a very different tack in Sup 2.0, and
1433 > not deal with IMAP at all. Sup will maintain its own document store, and
1434 > it's going to be up to the user to insert your mail into it.
1435
1436 After reading your blog posts this was the one thing I really wanted
1437 to comment on.
1438
1439 I think this is a mistake. By all means separate the document index
1440 from the viewer, but I'd advise against attempting to be the warehouse
1441 for the data. The most important thing needed to play nicely is to
1442 gracefully handle the case of data going missing from the source;
1443 sure, you can do that by always copying the data up front, but that's
1444 a blunt instrument that destroys several of the other advantages of
1445 the current sup.
1446
1447 My suggestion: Separate the indexing and querying of the index from
1448 the sources. Make it the responsibility of the viewer component to
1449 fetch the full documents from the sources and to fail gracefully when
1450 a query returns a document that's no longer available. Give the
1451 viewer a hook so that with the appropriate plug-in, certain indexing
1452 updates (like spam-tagging) can be pushed back to the source at the
1453 same time. (It's up to the plug-in to decide how.)
1454
1455 If you have that, you can still use your own document source into
1456 which you dump everything.
1457
1458 > I know that's probably not the answer you want. But I have no desire to
1459 > spend the requisite years of my life dealing with with hokey IMAP
1460 > servers, Ruby's hokey IMAP libraries, and everything in between.
1461
1462 I'm not suggesting (or even encouraging) that sup become a
1463 full-fledged IMAP client.
1464
1465 From marcus-sup@bar-coded.net Mon Aug 25 16:55:40 2008
1466 From: marcus-sup@bar-coded.net (Marcus Williams)
1467 Date: Mon, 25 Aug 2008 21:55:40 +0100
1468 Subject: [sup-talk] Some comments on sup-0.6
1469 In-Reply-To: <6bb609560808231615o1b7dc71eh48d192375e46cf8c@mail.gmail.com>
1470 References: <6bb609560808231615o1b7dc71eh48d192375e46cf8c@mail.gmail.com>
1471 Message-ID: <1219697254-sup-546@tomsk>
1472
1473 On 24.8.2008, barton.schaefer wrote:
1474 > There's either no on-screen help for how one builds up a search
1475 > expression, or it's simply too hard to find that help, and in
1476 > particular it wasn't obvious how one searches for all messages having
1477 > a certain label (I was expecting maybe something like gmail's
1478 > label:Xyz syntax).
1479
1480 Off the top of my head, some search expressions that are possible in
1481 sup:
1482
1483 From/to/subject searches:
1484
1485 from:email at domain.tld
1486 to:email at domain.tld
1487 subject:*wildcards*
1488
1489 ... wildcards are useful in from/to/cc searches as well "from:will*"
1490
1491 Date searches:
1492
1493 on:(16th feb)
1494 before:yesterday
1495 after:(last friday)
1496 during:(last week)
1497
1498 (note that because search results are returned as threads you can get
1499 messages outside of your date bounds because the thread containing the
1500 searched message may have messages outside the bounds if that makes
1501 sense).
1502
1503 Attachments:
1504
1505 has:attachment (attachment is a label)
1506 filetype:xls
1507 filename:thisisafilename.txt
1508
1509 (Use brackets to specify a filename with spaces)
1510
1511 Labels:
1512
1513 is:read
1514 is:spam
1515 is:deleted
1516 has:somelabel
1517 label:someotherlabel
1518
1519 Phrases are treated as searches on the body text. Combinations work
1520 and are treated as conjunctions/ands as far as I'm aware.
1521
1522 Hope that helps,
1523
1524 Marcus
1525
1526 From steve@patter.mine.nu Mon Aug 25 18:09:34 2008
1527 From: steve@patter.mine.nu (Stephen Patterson)
1528 Date: Mon, 25 Aug 2008 23:09:34 +0100
1529 Subject: [sup-talk] split threads?
1530 In-Reply-To: <1219624661-sup-6433@entry>
1531 References: <f96e0240808221523k7b273a78p969e5e3029abb57d@mail.gmail.com>
1532 <1219624661-sup-6433@entry>
1533 Message-ID: <20080825220933.GA27491@patter.mine.nu>
1534
1535 On 24 Aug 08, William Morgan (wmorgan-sup at masanjin.net) wrote:
1536 > All the time! I'd love to have this. I'd also love to figure out why
1537 > thread joining doesn't work, half the time.
1538
1539 For me (ok, I'm still using sup 0.5 because debian gem won't update to
1540 0.6) thread joining works until you exit sup. i.e. the join-status
1541 isn't saved back to the message index.
1542
1543 --
1544 Stephen Patterson :: steve at patter.me.uk :: http://patter.mine.nu/
1545 GPG: B416F0DE :: Jabber: patter at jabber.earth.li
1546 "Don't be silly, Minnie. Who'd be walking round these cliffs with a gas oven?"
1547 -------------- next part --------------
1548 A non-text attachment was scrubbed...
1549 Name: not available
1550 Type: application/pgp-signature
1551 Size: 197 bytes
1552 Desc: Digital signature
1553 URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20080825/9f27b9b4/attachment.bin>
1554
1555 From bdwalton@gmail.com Mon Aug 25 19:18:10 2008
1556 From: bdwalton@gmail.com (Ben Walton)
1557 Date: Mon, 25 Aug 2008 19:18:10 -0400
1558 Subject: [sup-talk] split threads?
1559 In-Reply-To: <20080825220933.GA27491@patter.mine.nu>
1560 References: <f96e0240808221523k7b273a78p969e5e3029abb57d@mail.gmail.com>
1561 <1219624661-sup-6433@entry> <20080825220933.GA27491@patter.mine.nu>
1562 Message-ID: <f96e0240808251618y116ad5b6qf2c3141004858711@mail.gmail.com>
1563
1564 > For me (ok, I'm still using sup 0.5 because debian gem won't update to
1565 > 0.6) thread joining works until you exit sup. i.e. the join-status
1566 > isn't saved back to the message index.
1567
1568 Although I haven't tried joining threads since updating to 0.6, I
1569 experienced the same behaviour you describe. It's not persistent, but
1570 it always word well during a session.
1571
1572 -Ben
1573 --
1574 ---------------------------------------------------------------------------------------------------------------------------
1575 Ben Walton <bdwalton at gmail.com>
1576
1577 When one person suffers from a delusion, it is called insanity. When
1578 many people suffer from a delusion it is called Religion.
1579 Robert M. Pirsig, Zen and the Art of Motorcycle Maintenance
1580
1581 ---------------------------------------------------------------------------------------------------------------------------
1582