community/pipermail-archives/sup-devel/2011-10.txt (16779B) - raw
1 From dmishd@gmail.com Sat Oct 8 11:15:28 2011
2 From: dmishd@gmail.com (Hamish D)
3 Date: Sat, 8 Oct 2011 16:15:28 +0100
4 Subject: [sup-devel] Time for sup 0.13?
5 Message-ID: <CAOxvSbdWXmHQ78eDqE3Hq5L9m_xDBwpwA18vFdDtTTrig-QJ6Q@mail.gmail.com>
6
7 Hello all
8
9 I'm thinking it might be time to bundle up the last year of sup
10 development and push it out there. So if no one objects within a week
11 I'll merge next into master. I'll notify this list and sup-talk, and
12 give more people a chance to try it out and see if there are any
13 regressions. Assuming it's alright we should be able to make it sup
14 0.13 in November.
15
16 Of course William or Rich will need to push the gem out there as I
17 don't have access.
18
19 Hamish Downer
20
21 From eg@gaute.vetsj.com Sat Oct 8 12:49:52 2011
22 From: eg@gaute.vetsj.com (Gaute Hope)
23 Date: Sat, 08 Oct 2011 18:49:52 +0200
24 Subject: [sup-devel] Time for sup 0.13?
25 In-Reply-To: <CAOxvSbdWXmHQ78eDqE3Hq5L9m_xDBwpwA18vFdDtTTrig-QJ6Q@mail.gmail.com>
26 References: <CAOxvSbdWXmHQ78eDqE3Hq5L9m_xDBwpwA18vFdDtTTrig-QJ6Q@mail.gmail.com>
27 Message-ID: <1318092478-sup-5464@qwerzila>
28
29 Excerpts from Hamish D's message of 2011-10-08 17:15:28 +0200:
30 > I'm thinking it might be time to bundle up the last year of sup
31 > development and push it out there. So if no one objects within a week
32 > I'll merge next into master. I'll notify this list and sup-talk, and
33 > give more people a chance to try it out and see if there are any
34 > regressions. Assuming it's alright we should be able to make it sup
35 > 0.13 in November.
36
37 Yei! I favour.
38
39 - Gaute
40
41 From dmishd@gmail.com Sun Oct 9 13:20:36 2011
42 From: dmishd@gmail.com (Hamish D)
43 Date: Sun, 9 Oct 2011 18:20:36 +0100
44 Subject: [sup-devel] Playing with heliotrope/turnsole
45 Message-ID: <CAOxvSbeMnuDRgkGupPMxcodq54Y=V38FPWq0893BOLgWT+bVxw@mail.gmail.com>
46
47 Hello
48
49 I've finally got around to having a bit more of a play with
50 turnsole/heliotrope, and I have a few questions that don't appear to
51 be answered by the README files.
52
53 Firstly, I just tried sending an email using turnsole and got a 500,
54 as heliotrope is expecting a particular sendmail command to work.
55 Looking through the code I find there is a sendmail hook, but there
56 doesn't appear to be a --list-hooks command in heliotrope-add or
57 heliotrope-server, or any documentation for the hooks. So I've started
58 trying to get it to work and put stuff on the wiki -
59 http://sup.rubyforge.org/wiki/wiki.pl?Heliotrope_Sendmail - still a
60 work in progress at the moment, though if anyone has a working hook
61 for msmtp I'd appreciate it :)
62
63 I've also started a wiki page to put general heliotrope/turnsole stuff
64 - http://sup.rubyforge.org/wiki/wiki.pl?Heliotrope_And_Turnsole
65
66 (As an aside I've noticed there's a little wiki vandalism going on,
67 but currently little enough that the occasional manual check should be
68 OK.)
69
70 Right off to add a few bug reports
71
72 Hamish
73
74 From wmorgan-sup@masanjin.net Sun Oct 9 15:27:48 2011
75 From: wmorgan-sup@masanjin.net (William Morgan)
76 Date: Sun, 09 Oct 2011 19:27:48 +0000
77 Subject: [sup-devel] Playing with heliotrope/turnsole
78 In-Reply-To: <CAOxvSbeMnuDRgkGupPMxcodq54Y=V38FPWq0893BOLgWT+bVxw@mail.gmail.com>
79 References: <CAOxvSbeMnuDRgkGupPMxcodq54Y=V38FPWq0893BOLgWT+bVxw@mail.gmail.com>
80 Message-ID: <1318188240-sup-1604@masanjin.net>
81
82 Reformatted excerpts from Hamish D's message of 2011-10-09:
83 > I've finally got around to having a bit more of a play with
84 > turnsole/heliotrope, and I have a few questions that don't appear to
85 > be answered by the README files.
86
87 Great! It's still definitely a work in progress, so expect a few rought
88 edges, but I've been using it fulltime for the past few months.
89
90 > Looking through the code I find there is a sendmail hook, but there
91 > doesn't appear to be a --list-hooks command in heliotrope-add or
92 > heliotrope-server, or any documentation for the hooks.
93
94 Yeah, adding a --list-hooks is TBD. Feel free to make an issue to track
95 this.
96
97 > So I've started trying to get it to work and put stuff on the wiki -
98 > http://sup.rubyforge.org/wiki/wiki.pl?Heliotrope_Sendmail
99
100 Awesome. Thank you.
101 --
102 William <wmorgan-sup at masanjin.net>
103
104 From dmishd@gmail.com Sun Oct 9 16:26:01 2011
105 From: dmishd@gmail.com (Hamish D)
106 Date: Sun, 9 Oct 2011 21:26:01 +0100
107 Subject: [sup-devel] Playing with heliotrope/turnsole
108 In-Reply-To: <1318188240-sup-1604@masanjin.net>
109 References: <CAOxvSbeMnuDRgkGupPMxcodq54Y=V38FPWq0893BOLgWT+bVxw@mail.gmail.com>
110 <1318188240-sup-1604@masanjin.net>
111 Message-ID: <CAOxvSbcpFOH-W1NSzx8no83c-2uOSOdqJovOA6RHNRyViwxjfw@mail.gmail.com>
112
113 >> So I've started trying to get it to work and put stuff on the wiki -
114 >> http://sup.rubyforge.org/wiki/wiki.pl?Heliotrope_Sendmail
115
116 One thing I wonder - is it possible to import labels from sup somehow?
117
118 My mailstore has lots of labels I've added by hand over time and I
119 wouldn't want to lost that information. (The mailstore I have in mind
120 is mbox, but I'm sure others would be interested).
121
122 Hamish
123
124 From wmorgan-sup@masanjin.net Sun Oct 9 17:19:42 2011
125 From: wmorgan-sup@masanjin.net (William Morgan)
126 Date: Sun, 09 Oct 2011 21:19:42 +0000
127 Subject: [sup-devel] Playing with heliotrope/turnsole
128 In-Reply-To: <CAOxvSbcpFOH-W1NSzx8no83c-2uOSOdqJovOA6RHNRyViwxjfw@mail.gmail.com>
129 References: <CAOxvSbeMnuDRgkGupPMxcodq54Y=V38FPWq0893BOLgWT+bVxw@mail.gmail.com>
130 <1318188240-sup-1604@masanjin.net>
131 <CAOxvSbcpFOH-W1NSzx8no83c-2uOSOdqJovOA6RHNRyViwxjfw@mail.gmail.com>
132 Message-ID: <1318195085-sup-6406@masanjin.net>
133
134 Reformatted excerpts from Hamish D's message of 2011-10-09:
135 > One thing I wonder - is it possible to import labels from sup somehow?
136
137 I'm working on the Sup upgrade process. It's a little complicated
138 because we need a way to merge multiple sup sources into one, and right
139 now Heliotrope's LIFO ordering constraint makes that complicated. But
140 I have a plan.
141 --
142 William <wmorgan-sup at masanjin.net>
143
144 From eg@gaute.vetsj.com Thu Oct 13 06:10:27 2011
145 From: eg@gaute.vetsj.com (Gaute Hope)
146 Date: Thu, 13 Oct 2011 12:10:27 +0200
147 Subject: [sup-devel] [PATCH] Don't fail on empty lines while expanding
148 Message-ID: <1318500554-sup-8811@qwerzila>
149
150 While expanding an GPG signature which must have contained a line that
151 ended up as nil while chomp'ing, chomp will crash. This patch filters
152 out lines which are nil.
153 ---
154 lib/sup/modes/thread-view-mode.rb | 2 +-
155 1 files changed, 1 insertions(+), 1 deletions(-)
156
157 diff --git a/lib/sup/modes/thread-view-mode.rb b/lib/sup/modes/thread-view-mode.rb
158 index 9fcc45d..ec1a82e 100644
159 --- a/lib/sup/modes/thread-view-mode.rb
160 +++ b/lib/sup/modes/thread-view-mode.rb
161 @@ -846,7 +846,7 @@ private
162 else
163 width = buffer.content_width
164 end
165 - lines = lines.map { |l| l.chomp.wrap width }.flatten
166 + lines = lines.map { |l| l.chomp.wrap width if l }.flatten
167 end
168 return lines
169 end
170 --
171 1.7.7
172
173
174 From dmishd@gmail.com Sun Oct 16 08:09:41 2011
175 From: dmishd@gmail.com (Hamish D)
176 Date: Sun, 16 Oct 2011 13:09:41 +0100
177 Subject: [sup-devel] Preparing for sup 0.13
178 Message-ID: <CAOxvSbcBz11N1Ac_fr970dPRqDv=e89xzicZoLbH+zTSJTEpcg@mail.gmail.com>
179
180 I've merged the next branch into master in preparation for releasing
181 sup 0.13. So this is a call for people to try it out and report any
182 problems they have before we push it out the door. For basic details
183 about running from git see
184 http://sup.rubyforge.org/wiki/wiki.pl?Running_From_Git
185
186 The major changes since sup 0.12 are:
187
188 * crypto stuff rewritten to use the gpgme library, leading to smoother
189 operations with encrypted email.
190 * add an option for whether sent mail is archived
191 * added an account selector when composing email for those who have
192 multiple possible from addresses
193 * added an asynchronous edit mode - this allows you to carry on using
194 sup while composing a message in an external editor
195
196 along with various bug fixes large and small.
197
198 I'm hoping we can push out 0.13 in November.
199
200 Hamish
201
202 From marka@pobox.com Tue Oct 18 09:46:27 2011
203 From: marka@pobox.com (Mark Alexander)
204 Date: Tue, 18 Oct 2011 09:46:27 -0400
205 Subject: [sup-devel] [sup-talk] Preparing for sup 0.13
206 In-Reply-To: <CAOxvSbcBz11N1Ac_fr970dPRqDv=e89xzicZoLbH+zTSJTEpcg@mail.gmail.com>
207 References: <CAOxvSbcBz11N1Ac_fr970dPRqDv=e89xzicZoLbH+zTSJTEpcg@mail.gmail.com>
208 Message-ID: <1318945224-sup-126@bloovis.org>
209
210 Excerpts from Hamish D's message of Sun Oct 16 08:09:41 -0400 2011:
211 > * added an asynchronous edit mode - this allows you to carry on using
212 > sup while composing a message in an external editor
213
214 I'm not having much luck with this feature. I was able to write an
215 async-edit hook that spawned my editor in a separate gnome-terminal
216 window. But when I exited async-edit mode, sup started responding to
217 keystrokes weirdly. I tried to discard the message I had just
218 composed using 'x', so sup asked if I wanted to discard the message,
219 and when I hit 'y', it sent the message instead of discarding it.
220 After that, sup behaved as if every other keystroke was being
221 discarded, and I had to quit and restart.
222
223 Other than that, things look good.
224
225 From dmishd@gmail.com Tue Oct 18 13:58:40 2011
226 From: dmishd@gmail.com (Hamish D)
227 Date: Tue, 18 Oct 2011 18:58:40 +0100
228 Subject: [sup-devel] [sup-talk] Preparing for sup 0.13
229 In-Reply-To: <1318945224-sup-126@bloovis.org>
230 References: <CAOxvSbcBz11N1Ac_fr970dPRqDv=e89xzicZoLbH+zTSJTEpcg@mail.gmail.com>
231 <1318945224-sup-126@bloovis.org>
232 Message-ID: <CAOxvSbchWGomtdFSv1yATD1=PvQ0zHZjfrdYx1uJk7RgTqb=CA@mail.gmail.com>
233
234 On 18 October 2011 14:46, Mark Alexander <marka at pobox.com> wrote:
235 > Excerpts from Hamish D's message of Sun Oct 16 08:09:41 -0400 2011:
236 >> * added an asynchronous edit mode - this allows you to carry on using
237 >> sup while composing a message in an external editor
238 >
239 > I'm not having much luck with this feature. ?I was able to write an
240 > async-edit hook that spawned my editor in a separate gnome-terminal
241 > window. ?But when I exited async-edit mode, sup started responding to
242 > keystrokes weirdly. ?I tried to discard the message I had just
243 > composed using 'x', so sup asked if I wanted to discard the message,
244 > and when I hit 'y', it sent the message instead of discarding it.
245 > After that, sup behaved as if every other keystroke was being
246 > discarded, and I had to quit and restart.
247
248 Could you email me your hook so I can check if there is anything in it
249 that might cause trouble? I've used the mode myself a bit and not hit
250 that issue.
251
252 I guess it's not really a regression as the feature didn't exist in
253 sup 0.12, but would still be good to sort it out ...
254
255 Hamish
256
257 From marka@pobox.com Wed Oct 19 10:31:29 2011
258 From: marka@pobox.com (Mark Alexander)
259 Date: Wed, 19 Oct 2011 10:31:29 -0400
260 Subject: [sup-devel] [sup-talk] Preparing for sup 0.13
261 In-Reply-To: <CAOxvSbcBz11N1Ac_fr970dPRqDv=e89xzicZoLbH+zTSJTEpcg@mail.gmail.com>
262 References: <CAOxvSbcBz11N1Ac_fr970dPRqDv=e89xzicZoLbH+zTSJTEpcg@mail.gmail.com>
263 Message-ID: <1319034152-sup-5416@bloovis.org>
264
265 Excerpts from Hamish D's message of Sun Oct 16 08:09:41 -0400 2011:
266 > * added an account selector when composing email for those who have
267 > multiple possible from addresses
268
269 I'm having a problem with this feature, too.
270
271 I have two main email accounts, one for personal email and one for
272 work email. My before-edit.rb hook figures out which account to use
273 as the sender (the "From" header) by looking at the recipients (the
274 "To" header). This worked with sup 0.12, but with 0.13 the sender is
275 changed back to the default as soon as I exit the editor.
276
277 I see that Sascha Silbe said something about this seven months ago:
278
279 > This one would possibly break my workflow. My From address is chosen in
280 > the before-edit hook based on the set of recipients. Since you only
281 > call before-edit once with headers_full as headers, whatever From
282 > address gets chosen for the initial reply mode will "stick".
283
284 Here's the sanitized before-edit.rb hook, in case that helps:
285
286 unless header["In-reply-to"]
287 if header["To"] =~ /widgets/
288 to = header["To"]
289 info "Sending as widgets, to = #{to}"
290 header["From"] = "Mark Alexander <marka at widgets.com>"
291 else
292 to = header["To"]
293 info "Sending as pobox, to = #{to}"
294 header["From"] = "Mark Alexander <marka at pobox.com>"
295 end
296 end
297
298 From marka@pobox.com Thu Oct 20 09:18:01 2011
299 From: marka@pobox.com (Mark Alexander)
300 Date: Thu, 20 Oct 2011 09:18:01 -0400
301 Subject: [sup-devel] [sup-talk] Preparing for sup 0.13
302 In-Reply-To: <1319034152-sup-5416@bloovis.org>
303 References: <CAOxvSbcBz11N1Ac_fr970dPRqDv=e89xzicZoLbH+zTSJTEpcg@mail.gmail.com>
304 <1319034152-sup-5416@bloovis.org>
305 Message-ID: <1319116525-sup-839@bloovis.org>
306
307 Excerpts from Mark Alexander's message of Wed Oct 19 10:31:29 -0400 2011:
308 > Excerpts from Hamish D's message of Sun Oct 16 08:09:41 -0400 2011:
309 > > * added an account selector when composing email for those who have
310 > > multiple possible from addresses
311 >
312 > I'm having a problem with this feature, too.
313 >
314 > I have two main email accounts, one for personal email and one for
315 > work email. My before-edit.rb hook figures out which account to use
316 > as the sender (the "From" header) by looking at the recipients (the
317 > "To" header). This worked with sup 0.12, but with 0.13 the sender is
318 > changed back to the default as soon as I exit the editor.
319
320 I'm trying out the attached fix, and so far it seems to work.
321 it simply moves the calling of the before-edit hook before
322 the creation of the account selector.
323 -------------- next part --------------
324 A non-text attachment was scrubbed...
325 Name: before-edit.patch
326 Type: application/octet-stream
327 Size: 877 bytes
328 Desc: not available
329 URL: <http://rubyforge.org/pipermail/sup-devel/attachments/20111020/5c9b47e7/attachment.obj>
330
331 From jmazzi@gmail.com Thu Oct 27 08:34:35 2011
332 From: jmazzi@gmail.com (Justin Mazzi)
333 Date: Thu, 27 Oct 2011 12:34:35 +0000 (UTC)
334 Subject: [sup-devel] Adding backward synchronization for Maildir sources
335 References: <1278693172-sup-6247@mailer> <1300032886-sup-4779@mailer>
336 Message-ID: <loom.20111027T143258-562@post.gmane.org>
337
338 Damien Leone <damien.leone <at> fensalir.fr> writes:
339
340 >
341 > Sup guys,
342 >
343 > Sorry for having been so long.
344 >
345 > What's new:
346 >
347 > - I added an option in sup-sync-back-maildir to merge the :replied and
348 > :forwarded labels/flags so the first time you run the script you
349 > should not lose any information on the IMAP side;
350 >
351 > - A way to detect if sup-sync-back-to-maildir should be executed in
352 > order to synchronize your index back to the Maildir source in order to
353 > prevent any loss of information. A magic file is written in the
354 > configuration directory everytime the script is executed and it is
355 > removed when the sync_back_to_maildir option is set from false to
356 > true;
357 >
358 > - I fixed a case when messages were not properly updated when they
359 > were remotely modified.
360 >
361 > I have pushed the last commits to the maildir-sync branch [0], it is
362 > rebased from master. I also have a branch rebased from next on my own
363 > repository if you'd rather a more up to date branch [1].
364 >
365 > Please test and review! For more informations and a howto, read the
366 > message quoted below this mail.
367 >
368 > [0] http://gitorious.org/sup/mainline/commits/maildir-sync
369 > [1] http://git.fensalir.fr/?p=dleone/sup.git
370
371 Hey,
372
373 The syncing is working pretty well for me except for one thing (with Gmail).
374
375 When archiving a message in sup it doesn't remove the Inbox label
376 from the message. Removing the Inbox label from the message is
377 what makes the email disappear from other clients, like a
378 smartphone.
379
380 - Justin Mazzi
381
382
383
384
385 From flavio@castelli.name Sat Oct 29 06:39:12 2011
386 From: flavio@castelli.name (Flavio Castelli)
387 Date: Sat, 29 Oct 2011 12:39:12 +0200
388 Subject: [sup-devel] Sup and imap
389 Message-ID: <CAAs+i9JMHw9_TLohiF-jvq4q_g16ao+Au4mPUtwfv=yCtNY-TA@mail.gmail.com>
390
391 Hello I would like to know the status of the IMAP support. I read some
392 entries on the wiki talking about it but they are a bit outdated.
393
394 Is now possible to propagate the actions performed via sup back to the
395 IMAP server?
396
397 Thanks in advance
398 Flavio
399
400 From michael+sup@stapelberg.de Sat Oct 29 08:05:52 2011
401 From: michael+sup@stapelberg.de (Michael Stapelberg)
402 Date: Sat, 29 Oct 2011 13:05:52 +0100
403 Subject: [sup-devel] Sup and imap
404 In-Reply-To: <CAAs+i9JMHw9_TLohiF-jvq4q_g16ao+Au4mPUtwfv=yCtNY-TA@mail.gmail.com>
405 References: <CAAs+i9JMHw9_TLohiF-jvq4q_g16ao+Au4mPUtwfv=yCtNY-TA@mail.gmail.com>
406 Message-ID: <1319889919-sup-7626@stapelberg.de>
407
408 Hi Flavio,
409
410 Excerpts from Flavio Castelli's message of 2011-10-29 11:39:12 +0100:
411 > Hello I would like to know the status of the IMAP support. I read some
412 > entries on the wiki talking about it but they are a bit outdated.
413 sup doesn?t have IMAP support due to the ruby IMAP libraries being buggy.
414
415 > Is now possible to propagate the actions performed via sup back to the
416 > IMAP server?
417 Use offlineimap, it can sync in both directions.
418
419 Best regards,
420 Michael
421