community/pipermail-archives/sup-talk/2013-05.txt (18546B) - raw
1 From eg@gaute.vetsj.com Tue May 7 11:54:22 2013
2 From: eg@gaute.vetsj.com (Gaute Hope)
3 Date: Tue, 07 May 2013 13:54:22 +0200
4 Subject: [sup-talk] [sup-devel] sup 0.13 - please test
5 In-Reply-To: <CAOxvSbeLRoCwy2THkKa4TKsNqdsx9n-M5BxrZHGfPEUjfEWjSg@mail.gmail.com>
6 References: <CAOxvSbeLRoCwy2THkKa4TKsNqdsx9n-M5BxrZHGfPEUjfEWjSg@mail.gmail.com>
7 Message-ID: <5188EB6E.8070504@gaute.vetsj.com>
8
9 On 28. april 2013 22:32, Hamish D wrote:
10 > We'd like to get version 0.13 of sup out soon. There's a fair bit of
11 > work gone into sup since 0.12 was released (in January 2011) that it
12 > would be good to get out there. Once that is done we can then work on
13 > the bigger goals we have for 0.14 - see
14 > https://github.com/sup-heliotrope/sup/wiki/Development#roadmap for
15 > those plans.
16 >
17 > So the question is, are there any serious bugs that we should fix
18 > before releasing 0.13?
19
20 Greetings sup-devel and sup-talk,
21
22
23 Thanks to several contributors I think we should be getting ready for
24 0.13 now soon, we've removed a lot of old and deprecated stuff and
25 generally cleaned a bit up.
26
27 There is a new web page: http://supmua.org which is getting in shape and
28 a wiki which is quickly growing: https://github.com/sup-heliotrope/sup/wiki
29
30 We have forked our own version of ncursesw (ncursesw-sup) which now is a
31 dependency for sup [1].
32
33 To be able to do the next release we need some testing of the current
34 state of 'develop' and the new ncursesw-sup gem. For instructions on how
35 to help out with testing the latest git version (develop) check out:
36 https://github.com/sup-heliotrope/sup/wiki/Running-from-git
37
38 If you have any problems or questions please ask.
39
40 Report issues to: https://github.com/sup-heliotrope/sup/issues
41
42
43 [1] https://rubygems.org/gems/ncursesw-sup
44
45
46 Regards,
47 Gaute
48
49 From eg@gaute.vetsj.com Wed May 15 08:30:27 2013
50 From: eg@gaute.vetsj.com (Gaute Hope)
51 Date: Wed, 15 May 2013 10:30:27 +0200
52 Subject: [sup-talk] Release 0.13.0
53 Message-ID: <519347A3.4070500@gaute.vetsj.com>
54
55 -----BEGIN PGP SIGNED MESSAGE-----
56 Hash: SHA1
57
58 Greetings fellow Suppers,
59
60 We have just released version 0.13.0 at Rubygems:
61
62 https://rubygems.org/gems/sup
63
64 to install:
65
66 gem install sup
67
68 for more information check out the wiki:
69
70 https://github.com/sup-heliotrope/sup/wiki
71
72 or the new web site:
73
74 http://supmua.org
75
76
77 Thanks a lot to all who have contributed over the last years since the
78 previous release, and in particular all those who have been part of
79 effort to get Sup going again and getting this release out as well as
80 William Morgan who has let us keep working on Sup. I hope it will last!
81
82
83 Please report bugs too:
84
85 https://github.com/sup-heliotrope/sup/issues
86
87
88 - - The Sup maintainers
89
90
91 Note: The gem has been signed with my key (included below), note
92 however that Rubygems signing is still only in its infancy.
93
94 - -----BEGIN CERTIFICATE-----
95 MIIDVDCCAjygAwIBAgIBADANBgkqhkiG9w0BAQUFADBQMQswCQYDVQQDDAJlZzEV
96 MBMGCgmSJomT8ixkARkWBWdhdXRlMRUwEwYKCZImiZPyLGQBGRYFdmV0c2oxEzAR
97 BgoJkiaJk/IsZAEZFgNjb20wHhcNMTMwNTA4MTAzODQ3WhcNMTQwNTA4MTAzODQ3
98 WjBQMQswCQYDVQQDDAJlZzEVMBMGCgmSJomT8ixkARkWBWdhdXRlMRUwEwYKCZIm
99 iZPyLGQBGRYFdmV0c2oxEzARBgoJkiaJk/IsZAEZFgNjb20wggEiMA0GCSqGSIb3
100 DQEBAQUAA4IBDwAwggEKAoIBAQC7sNc5zY4MrYB7eywE/aK2IoDqpM9lq4ZFlHzt
101 Pmq1LG6ah2lu/HfjqxiPoqwY7QkdSOGDLSk7G8YBqDA/tODhkPPSTqxBDzYyCO46
102 haWTtoN5tJkxIDJKp1nVXHi0Mlb4GJVKd9P0q95BeBYBfs8vyPN+y4b4Gebgx9U3
103 KqMDbe5h9MAPZGmtiRFMb3ugmiujDm7v8fACa5EtSvK/lxMkRDglecT/knE99NYI
104 l35SO/Bune1bxYmkwW64mQ4wRlGVeAnX+19msALfS9rdJL26dfW2LgqWi5QoVTBH
105 KNKTl/i3fxK0mzgtnoRCWdMJQFNNonFTnPUUawi1c9Kh4AdPAgMBAAGjOTA3MAkG
106 A1UdEwQCMAAwHQYDVR0OBBYEFJNCOxL0SWcbW2M+DIEUzAMz1bZsMAsGA1UdDwQE
107 AwIEsDANBgkqhkiG9w0BAQUFAAOCAQEAr3QUayd0geBDExO+WwzaEPAuUZ3zWQYG
108 G9vrplCkmJtjS/X/wVAef7Jn/V5MNkXKXsiOgXJXki+n7HulNZUf1rzr7Un96gVJ
109 1hq/ZTuapnPpstBqqdv60RB8HNGydHQeEz6us5z3nj+KchPqJ657Dz8oX/Nm6/24
110 7QSQpCh8xBYdSWEpoIE0zUSY77LtVTRVwIr9uDpWTTr9kCVBINBsOQNjWKruEWjV
111 +JMuDs+iWefpF4R3BySoOc1Q4WoES3+oc0qo37MsAZyfnQIPTZkyLZCMxeL6Mha4
112 hFc2yANBj8voaY5C74Cg2VqExtcnSaxUtW9wC4w5hOlg0AVfb1JWzg==
113 - -----END CERTIFICATE-----
114 -----BEGIN PGP SIGNATURE-----
115 Version: GnuPG v2.0.19 (GNU/Linux)
116 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
117
118 iQIcBAEBAgAGBQJRk0eiAAoJEJgnp+igdJAj58oP/2APxYsJ3RWtlhFGDk5IVSeW
119 XNxw449fyRB1pnsyUvFvtkf0IU6SzVF/lV+Iq2mNIgGlsN1wKU5zk92Ic3cm0KAh
120 dO8YmvQP46NV0UqZWSg6cu91cMbBOUD1KIpww633fEjN7N9fHuAO1BWZlQqpTt/S
121 Y7bkpCCQWzwcY9yDtiZDp1qXQoLvxTg8epsIV1XwgGi9G/h0IAXZIG2VqmQl/80T
122 0VteWfGHZ/PWa+34/101Q5uN8SXo+HLW2o4UD0lPSL0RRoQE0AkilbctzOQT6TE4
123 lYmhPmgFDBoW5XWv73JxkS8y95BcYCUl2Q3w0KuyeYJeAIYWaU8WTCebYEBMnuud
124 Lob97x/o+YA8SQylSnJxOyT8kTqvH4ZG7X2yEeJztJQaNagUlKIuvujF/s1lCaRi
125 2O5kcI6UaAC6yu3XUwXESsXOQ0cUQnbG6P/CZtBXDFaeYqMHq5KSbjm99h+s8l6/
126 97VQCxa2JYaaQb5wHtk0jrPAmpbA+EXJ4LzlMZeDMRf7+J1Ag8Y6XDRP2BN2p6Q8
127 QKNoHrrPpCPZyXDxoMYHVoGl4UYXCS0n8jTdUG62b5fJjs9A5YayT4PiXtmxs/B3
128 HYsDc9jGsoZyduJWI36pPQgc9wb65rpRLm1NMySokzp1zIydEmYZY8+Y+zXa2xba
129 31ciZlyNkN0TO/JmU34G
130 =Trft
131 -----END PGP SIGNATURE-----
132
133 From daniel@wagner-home.com Wed May 15 13:28:52 2013
134 From: daniel@wagner-home.com (Daniel Wagner)
135 Date: Wed, 15 May 2013 09:28:52 -0400
136 Subject: [sup-talk] Release 0.13.0
137 In-Reply-To: <519347A3.4070500@gaute.vetsj.com>
138 References: <519347A3.4070500@gaute.vetsj.com>
139 Message-ID: <bc80e24ca3b4a03743c11cbf854bd64f@seas.upenn.edu>
140
141 On 2013-05-15 04:30, Gaute Hope wrote:
142 > or the new web site:
143 >
144 > http://supmua.org
145
146 The new website seems to be down!
147 ~d
148
149 From eg@gaute.vetsj.com Wed May 15 14:38:21 2013
150 From: eg@gaute.vetsj.com (Gaute Hope)
151 Date: Wed, 15 May 2013 16:38:21 +0200
152 Subject: [sup-talk] Release 0.13.0
153 In-Reply-To: <bc80e24ca3b4a03743c11cbf854bd64f@seas.upenn.edu>
154 References: <519347A3.4070500@gaute.vetsj.com>
155 <bc80e24ca3b4a03743c11cbf854bd64f@seas.upenn.edu>
156 Message-ID: <51939DDD.4090507@gaute.vetsj.com>
157
158 On 15. mai 2013 15:28, Daniel Wagner wrote:
159 > On 2013-05-15 04:30, Gaute Hope wrote:
160 >> or the new web site:
161 >>
162 >> http://supmua.org
163 >
164 > The new website seems to be down!
165 > ~d
166
167 Seems to have been a glitch, is back up now.
168
169 https://status.github.com/messages
170
171 - gaute
172
173 From marka@pobox.com Fri May 17 16:51:57 2013
174 From: marka@pobox.com (Mark Alexander)
175 Date: Fri, 17 May 2013 12:51:57 -0400
176 Subject: [sup-talk] [PATCH] Fix search-for-next function when using Ruby 1.9
177 Message-ID: <1368809417-sup-3442@x200s>
178
179 [Note: I've submitted a pull request for this fix.]
180
181 The use of the 'n' key to search for the next occurrence
182 of a string stopped working when running sup in Ruby 1.9.
183 This simple patch fixes that problem.
184 ---
185 lib/sup/buffer.rb | 2 +-
186 1 file changed, 1 insertion(+), 1 deletion(-)
187
188 diff --git a/lib/sup/buffer.rb b/lib/sup/buffer.rb
189 index 444589a..859e0c7 100644
190 --- a/lib/sup/buffer.rb
191 +++ b/lib/sup/buffer.rb
192 @@ -271,7 +271,7 @@ EOS
193
194 def handle_input c
195 if @focus_buf
196 - if @focus_buf.mode.in_search? && c != CONTINUE_IN_BUFFER_SEARCH_KEY[0]
197 + if @focus_buf.mode.in_search? && c != CONTINUE_IN_BUFFER_SEARCH_KEY.ord
198 @focus_buf.mode.cancel_search!
199 @focus_buf.mark_dirty
200 end
201
202
203 From eg@gaute.vetsj.com Fri May 17 16:58:55 2013
204 From: eg@gaute.vetsj.com (Gaute Hope)
205 Date: Fri, 17 May 2013 18:58:55 +0200
206 Subject: [sup-talk] [PATCH] Fix search-for-next function when using Ruby
207 1.9
208 In-Reply-To: <1368809417-sup-3442@x200s>
209 References: <1368809417-sup-3442@x200s>
210 Message-ID: <519661CF.7040909@gaute.vetsj.com>
211
212 Thanks, is merged into develop and line-0.13-develop.
213
214 Regards, Gaute
215
216 On fr. 17. mai 2013 kl. 18.51 +0200, Mark Alexander wrote:
217 > [Note: I've submitted a pull request for this fix.]
218 >
219 > The use of the 'n' key to search for the next occurrence
220 > of a string stopped working when running sup in Ruby 1.9.
221 > This simple patch fixes that problem.
222 > ---
223 > lib/sup/buffer.rb | 2 +-
224 > 1 file changed, 1 insertion(+), 1 deletion(-)
225 >
226 > diff --git a/lib/sup/buffer.rb b/lib/sup/buffer.rb
227 > index 444589a..859e0c7 100644
228 > --- a/lib/sup/buffer.rb
229 > +++ b/lib/sup/buffer.rb
230 > @@ -271,7 +271,7 @@ EOS
231 >
232 > def handle_input c
233 > if @focus_buf
234 > - if @focus_buf.mode.in_search? && c != CONTINUE_IN_BUFFER_SEARCH_KEY[0]
235 > + if @focus_buf.mode.in_search? && c != CONTINUE_IN_BUFFER_SEARCH_KEY.ord
236 > @focus_buf.mode.cancel_search!
237 > @focus_buf.mark_dirty
238 > end
239 >
240 > _______________________________________________
241 > sup-talk mailing list
242 > sup-talk at rubyforge.org
243 > http://rubyforge.org/mailman/listinfo/sup-talk
244
245 From matthieu.rakotojaona@gmail.com Fri May 17 20:34:38 2013
246 From: matthieu.rakotojaona@gmail.com (Matthieu Rakotojaona)
247 Date: Fri, 17 May 2013 22:34:38 +0200
248 Subject: [sup-talk] Release 0.13.0
249 In-Reply-To: <519347A3.4070500@gaute.vetsj.com>
250 References: <519347A3.4070500@gaute.vetsj.com>
251 Message-ID: <1368822577-sup-3589@kpad>
252
253 Hey everyone,
254
255 Excerpts from Gaute Hope's message of mer. mai 15 10:30:27 +0200 2013:
256 > We have just released version 0.13.0 at Rubygems:
257
258 I'd like to thank every one of you for reviving sup. After having left
259 heliotrope on the side, I was longing for an alternative but couldn't
260 find anything as pleasant to hack on as heliotrope. I can now use all
261 the power of a search-driven MUA, and I can do it because you pushed it
262 to this release. You are awesome, thank you!
263
264 --
265 Matthieu Rakotojaona
266 -------------- next part --------------
267 A non-text attachment was scrubbed...
268 Name: signature.asc
269 Type: application/pgp-signature
270 Size: 836 bytes
271 Desc: not available
272 URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20130517/c730a38e/attachment.bin>
273
274 From bacuh@riseup.net Fri May 24 11:59:14 2013
275 From: bacuh@riseup.net (Sebastian Lipp)
276 Date: Fri, 24 May 2013 13:59:14 +0200
277 Subject: [sup-talk] Umlauts broken
278 Message-ID: <20130524115914.GA3518@eee.Speedport_W_504V_Typ_A>
279
280 Hi.
281
282 I was really happy as I heard, that sup is actively developed again. Too
283 long time ago I had to leave sup because it got broken more and more...
284
285 Just tried to install (via gem) and run it via rbenv under ruby
286 1.9.3-p327 and 1.9.3-p392. With both I have the problem that characters
287 like Umlauts are not show correctly. For example: "?" becomes "\xe4".
288
289 When setting $SUP_LOG_LEVEL to debug I get several of those lines:
290
291 couldn't transcode text from ASCII (ASCII) to UTF8 ("<20130523193529.GB30"...): got String::CheckError (unexpected encoding ASCII-8BIT)
292
293 I'm not sure if this is related to my encoding problems. Any of those
294 lines seem to be referencing to header lines.
295
296 I was long enough without sup so I can wait for the compatibility with
297 ruby 2.0.0 but I would really prefer to sup again sooner.
298
299 So have you any solution, work-around or patch at hand for this problem
300 or do you have any idea how I can help debug this problem?
301
302 LG
303 basti
304
305 --
306 react!OR :: Fr?hlingstr. 17 | 87439 Kempten
307 selbstverwaltetes JuZe :: Infoladen | Umsonstladen | Offener Raum
308 https://react.or.ke :: Telefon: 0831 52623689
309
310 Der react!OR lebt von Dingen, die anderswo ?brig sind. Aktuell gesucht:
311 Mehrfachstecker, Verl?ngerungskabel, N?hmaschine, Diktierger?t,
312 Papierschneidebrett, Dosen?ffner ... mehr: <https://react.or.ke/suche>
313
314 From eg@gaute.vetsj.com Fri May 24 14:22:51 2013
315 From: eg@gaute.vetsj.com (Gaute Hope)
316 Date: Fri, 24 May 2013 16:22:51 +0200
317 Subject: [sup-talk] Umlauts broken
318 In-Reply-To: <20130524115914.GA3518@eee.Speedport_W_504V_Typ_A>
319 References: <20130524115914.GA3518@eee.Speedport_W_504V_Typ_A>
320 Message-ID: <519F77BB.5010605@gaute.vetsj.com>
321
322
323
324 On 24. mai 2013 13:59, Sebastian Lipp wrote:
325 > Hi.
326 >
327 > I was really happy as I heard, that sup is actively developed again. Too
328 > long time ago I had to leave sup because it got broken more and more...
329 >
330 > Just tried to install (via gem) and run it via rbenv under ruby
331 > 1.9.3-p327 and 1.9.3-p392. With both I have the problem that characters
332 > like Umlauts are not show correctly. For example: "?" becomes "\xe4".
333 >
334 > When setting $SUP_LOG_LEVEL to debug I get several of those lines:
335 >
336 > couldn't transcode text from ASCII (ASCII) to UTF8 ("<20130523193529.GB30"...): got String::CheckError (unexpected encoding ASCII-8BIT)
337 >
338 > I'm not sure if this is related to my encoding problems. Any of those
339 > lines seem to be referencing to header lines.
340 >
341 > I was long enough without sup so I can wait for the compatibility with
342 > ruby 2.0.0 but I would really prefer to sup again sooner.
343 >
344 > So have you any solution, work-around or patch at hand for this problem
345 > or do you have any idea how I can help debug this problem?
346 >
347 > LG
348 > basti
349 >
350
351 Hi Sebastian,
352
353 Don't have the chance to go investigate much atm, but it could be
354 related to RMail and the usual lack of correct UTF-8 handling. I would
355 suggest you open an issue here though:
356
357 https://github.com/sup-heliotrope/sup/issues?state=open
358
359 otherwise it can easily disappear away..
360
361 If you are bold enough #61
362 (https://github.com/sup-heliotrope/sup/pull/61) have initial Mail
363 support for ruby 2.0, it would be interesting to see if the problem is
364 present there.
365
366 Note: this branch is incomplete and not usable yet for sending mail.
367
368 Also, hold on to problematic emails for testing later!
369
370 Regards, Gaute
371
372 From bacuh@riseup.net Sat May 25 14:32:37 2013
373 From: bacuh@riseup.net (Sebastian Lipp)
374 Date: Sat, 25 May 2013 16:32:37 +0200
375 Subject: [sup-talk] Umlauts broken
376 In-Reply-To: <519F77BB.5010605@gaute.vetsj.com>
377 References: <20130524115914.GA3518@eee.Speedport_W_504V_Typ_A>
378 <519F77BB.5010605@gaute.vetsj.com>
379 Message-ID: <20130525143236.GA29888@eee>
380
381 On 2013-05-24 04:22, Gaute Hope wrote:
382 > On 24. mai 2013 13:59, Sebastian Lipp wrote:
383 > > Just tried to install (via gem) and run it via rbenv under ruby
384 > > 1.9.3-p327 and 1.9.3-p392. With both I have the problem that characters
385 > > like Umlauts are not show correctly. For example: "?" becomes "\xe4".
386 >
387 > Don't have the chance to go investigate much atm, but it could be
388 > related to RMail and the usual lack of correct UTF-8 handling. I would
389 > suggest you open an issue here though:
390 >
391 > https://github.com/sup-heliotrope/sup/issues?state=open
392 >
393 > otherwise it can easily disappear away..
394
395 Do you thing my description is good enough to open a new issue?
396
397 > If you are bold enough #61
398 > (https://github.com/sup-heliotrope/sup/pull/61) have initial Mail
399 > support for ruby 2.0, it would be interesting to see if the problem is
400 > present there.
401
402 After bundle install and the branch's checkout it failed to load syck. A
403 `gem i syck` later it fails With
404
405 syck has been removed
406 /home/bacuh/.rbenv/versions/2.0.0-p0/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:in
407 `require':
408 /home/bacuh/.rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/rmail-1.0.0/lib/rmail/address.rb:694:
409 invalid multibyte escape: /\A[\200-\377\w!$%&\'*+\/=?^_\`{\}|~#-]+/m
410 (SyntaxError)
411
412 If you have a quick resolution for that I can go on and see if the
413 encoding problems still exist on this branch.
414
415 LG
416 basti
417
418 --
419 react!OR :: Fr?hlingstr. 17 | 87439 Kempten
420 selbstverwaltetes JuZe :: Infoladen | Umsonstladen | Offener Raum
421 https://react.or.ke :: Telefon: 0831 52623689
422
423 Der react!OR lebt von Dingen, die anderswo ?brig sind. Aktuell gesucht:
424 Mehrfachstecker, Verl?ngerungskabel, N?hmaschine, Diktierger?t,
425 Papierschneidebrett, Dosen?ffner ... mehr: <https://react.or.ke/suche>
426
427 From eg@gaute.vetsj.com Sat May 25 15:07:23 2013
428 From: eg@gaute.vetsj.com (Gaute Hope)
429 Date: Sat, 25 May 2013 17:07:23 +0200
430 Subject: [sup-talk] Umlauts broken
431 In-Reply-To: <20130525143236.GA29888@eee>
432 References: <20130524115914.GA3518@eee.Speedport_W_504V_Typ_A>
433 <519F77BB.5010605@gaute.vetsj.com> <20130525143236.GA29888@eee>
434 Message-ID: <51A0D3AB.6050401@gaute.vetsj.com>
435
436
437
438 On 25. mai 2013 16:32, Sebastian Lipp wrote:
439 > On 2013-05-24 04:22, Gaute Hope wrote:
440 >> On 24. mai 2013 13:59, Sebastian Lipp wrote:
441 >>> Just tried to install (via gem) and run it via rbenv under ruby
442 >>> 1.9.3-p327 and 1.9.3-p392. With both I have the problem that characters
443 >>> like Umlauts are not show correctly. For example: "?" becomes "\xe4".
444 >>
445 >> Don't have the chance to go investigate much atm, but it could be
446 >> related to RMail and the usual lack of correct UTF-8 handling. I would
447 >> suggest you open an issue here though:
448 >>
449 >> https://github.com/sup-heliotrope/sup/issues?state=open
450 >>
451 >> otherwise it can easily disappear away..
452 >
453 > Do you thing my description is good enough to open a new issue?
454 >
455 >> If you are bold enough #61
456 >> (https://github.com/sup-heliotrope/sup/pull/61) have initial Mail
457 >> support for ruby 2.0, it would be interesting to see if the problem is
458 >> present there.
459 >
460 > After bundle install and the branch's checkout it failed to load syck. A
461 > `gem i syck` later it fails With
462 >
463 > syck has been removed
464 > /home/bacuh/.rbenv/versions/2.0.0-p0/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:in
465 > `require':
466 > /home/bacuh/.rbenv/versions/2.0.0-p0/lib/ruby/gems/2.0.0/gems/rmail-1.0.0/lib/rmail/address.rb:694:
467 > invalid multibyte escape: /\A[\200-\377\w!$%&\'*+\/=?^_\`{\}|~#-]+/m
468 > (SyntaxError)
469 >
470 > If you have a quick resolution for that I can go on and see if the
471 > encoding problems still exist on this branch.
472
473 The pull request hasn't been merged into the official repo yet, so you'd
474 have to grab it from my repo:
475
476 git://github.com/gauteh/sup.git
477
478 (neither syck nor rmail is required)
479
480 Yes, I think so, these issues are diffuse.. but they re-appear all the
481 time. With a test-email to reproduce the issue things get easier.
482
483 Regards, Gaute
484
485 From ezyang@MIT.EDU Thu May 30 22:06:35 2013
486 From: ezyang@MIT.EDU (Edward Z. Yang)
487 Date: Thu, 30 May 2013 15:06:35 -0700
488 Subject: [sup-talk] A useful contacts list trick
489 Message-ID: <1369951537-sup-9257@javelin>
490
491 I had always been bothered by the fact that my contacts autocomplete
492 would never seem to work half of the time. I finally found out how
493 to vastly improve my it:
494
495 diff --git a/lib/sup/buffer.rb b/lib/sup/buffer.rb
496 index 444589a..077dc94 100644
497 --- a/lib/sup/buffer.rb
498 +++ b/lib/sup/buffer.rb
499 @@ -553,7 +553,7 @@ EOS
500 default = default_contacts.is_a?(String) ? default_contacts : default_contacts.map { |s| s.to_s }.join(", ")
501 default += " " unless default.empty?
502
503 - recent = Index.load_contacts(AccountManager.user_emails, :num => 10).map { |c| [c.full_address, c.email] }
504 + recent = Index.load_contacts(AccountManager.user_emails, :num => 100).map { |c| [c.full_address, c.email] }
505 contacts = ContactManager.contacts.map { |c| [ContactManager.alias_for(c), c.full_address, c.email] }
506
507 completions = (recent + contacts).flatten.uniq
508
509 Hope this helps someone else out :)
510
511 Cheers,
512 Edward
513