community/pipermail-archives/sup-talk/2013-06.txt (6844B) - raw
1 From skyronic@gmail.com Sat Jun 15 14:24:17 2013
2 From: skyronic@gmail.com (Anirudh Sanjeev)
3 Date: Sat, 15 Jun 2013 19:54:17 +0530
4 Subject: [sup-talk] Want to contribute to sup
5 Message-ID: <CAE4LD9q+CMMQeqfUwpQ9Dpz=+60dOdvV+Yuu3s+XTAKgwm7OMA@mail.gmail.com>
6
7 Hi,
8
9 I tried using sup in Jan 2010 [1] and used it for a while and was a little
10 disheartened when I didn't see a release for a while. Eventually I went
11 about using a regular client but I kept checking up on sup.
12
13 Today, I discover that the project is active again. And I am a better
14 programmer than the last time I tried to work on sup 3 years ago, so I feel
15 I can make some meaningful contributions. I will definitely try out the new
16 release after I get home.
17
18 I found that the offlineimap/Maildir approach to fetching email resulted in
19 emails remaining marked as "unread" on the server and web-clients. Is this
20 still the behavior when we use offlineimap to fetch the mail?
21
22 Thank you,
23 Anirudh
24
25
26 [1]: http://rubyforge.org/pipermail/sup-talk/2010-January/003726.html
27
28 --
29 Co-founder and Developer, RazorFlow
30 http://razorflow.com
31 -------------- next part --------------
32 An HTML attachment was scrubbed...
33 URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20130615/fca79bb2/attachment-0001.html>
34
35 From eg@gaute.vetsj.com Sat Jun 15 15:36:04 2013
36 From: eg@gaute.vetsj.com (Gaute Hope)
37 Date: Sat, 15 Jun 2013 17:36:04 +0200
38 Subject: [sup-talk] Want to contribute to sup
39 In-Reply-To: <CAE4LD9q+CMMQeqfUwpQ9Dpz=+60dOdvV+Yuu3s+XTAKgwm7OMA@mail.gmail.com>
40 References: <CAE4LD9q+CMMQeqfUwpQ9Dpz=+60dOdvV+Yuu3s+XTAKgwm7OMA@mail.gmail.com>
41 Message-ID: <1371310273-sup-6422@qwerzila>
42
43 Excerpts from Anirudh Sanjeev's message of 2013-06-15 16:24:17 +0200:
44 > I tried using sup in Jan 2010 [1] and used it for a while and was a little
45 > disheartened when I didn't see a release for a while. Eventually I went
46 > about using a regular client but I kept checking up on sup.
47 >
48 > Today, I discover that the project is active again. And I am a better
49 > programmer than the last time I tried to work on sup 3 years ago, so I feel
50 > I can make some meaningful contributions. I will definitely try out the new
51 > release after I get home.
52
53 Great! In case you're not aware of it, also check out the sup-devel list [1].
54
55
56 > I found that the offlineimap/Maildir approach to fetching email resulted in
57 > emails remaining marked as "unread" on the server and web-clients. Is this
58 > still the behavior when we use offlineimap to fetch the mail?
59
60
61 The work on syncing back status changes to IMAP (through maildir) is
62 going on in the maildir-sync branch [2]. It is not yet included in a
63 release, but it will hopefully soon be ready. Usage instructions [3] and
64 some development notes [4] are available in the wiki.
65
66
67 Regards, Gaute
68
69
70
71 [1] http://rubyforge.org/pipermail/sup-devel/
72 [2] https://github.com/sup-heliotrope/sup/tree/maildir-sync
73 [3] https://github.com/sup-heliotrope/sup/wiki/Maildir-Syncback
74 [4] https://github.com/sup-heliotrope/sup/wiki/Development%3A-Maildir-syncback
75
76 From eg@gaute.vetsj.com Fri Jun 21 12:07:19 2013
77 From: eg@gaute.vetsj.com (Gaute Hope)
78 Date: Fri, 21 Jun 2013 14:07:19 +0200
79 Subject: [sup-talk] Release 0.13.1
80 Message-ID: <1371816327-sup-6968@qwerzila>
81
82 Greetings,
83
84 I have just pushed version 0.13.1 of Sup to rubygems. This release holds
85 should still be Ruby 1.8 compatible and holds the backported patches
86 since the last release.
87
88 No big changes, but a number of fixes has been applied.
89
90 Regards, Gaute
91
92
93 From pearson@changedmy.name Sat Jun 22 02:10:29 2013
94 From: pearson@changedmy.name (James Pearson)
95 Date: Fri, 21 Jun 2013 19:10:29 -0700
96 Subject: [sup-talk] Release 0.13.1
97 In-Reply-To: <1371816327-sup-6968@qwerzila>
98 References: <1371816327-sup-6968@qwerzila>
99 Message-ID: <CA+ds9gJCfauTgS1LvrsOF0QREAKh9pKy=a550nj=1ZNi7wBvzA@mail.gmail.com>
100
101 I was going to ask why the tags on the Gitorious repo[0] hadn't been
102 updated, when I visited the (new!) website and saw that development has
103 moved onto Github[1] (and restarted!). I'm apparently very behind the
104 times - and perhaps now I should dig out those changes I made and submit
105 them...
106
107 Glad to see things moving along again.
108 - P
109
110 [0]: http://gitorious.org/sup/mainline
111 [1]: https://github.com/sup-heliotrope/sup
112
113
114 On Fri, Jun 21, 2013 at 5:07 AM, Gaute Hope <eg at gaute.vetsj.com> wrote:
115
116 > Greetings,
117 >
118 > I have just pushed version 0.13.1 of Sup to rubygems. This release holds
119 > should still be Ruby 1.8 compatible and holds the backported patches
120 > since the last release.
121 >
122 > No big changes, but a number of fixes has been applied.
123 >
124 > Regards, Gaute
125 >
126 > _______________________________________________
127 > sup-talk mailing list
128 > sup-talk at rubyforge.org
129 > http://rubyforge.org/mailman/listinfo/sup-talk
130 >
131 -------------- next part --------------
132 An HTML attachment was scrubbed...
133 URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20130621/dd6a7cd6/attachment.html>
134
135 From eg@gaute.vetsj.com Sat Jun 22 10:48:13 2013
136 From: eg@gaute.vetsj.com (Gaute Hope)
137 Date: Sat, 22 Jun 2013 12:48:13 +0200
138 Subject: [sup-talk] Release 0.13.1
139 In-Reply-To: <CA+ds9gJCfauTgS1LvrsOF0QREAKh9pKy=a550nj=1ZNi7wBvzA@mail.gmail.com>
140 References: <1371816327-sup-6968@qwerzila>
141 <CA+ds9gJCfauTgS1LvrsOF0QREAKh9pKy=a550nj=1ZNi7wBvzA@mail.gmail.com>
142 Message-ID: <1371897680-sup-4189@qwerzila>
143
144 Excerpts from James Pearson's message of 2013-06-22 04:10:29 +0200:
145 > I was going to ask why the tags on the Gitorious repo[0] hadn't been
146 > updated, when I visited the (new!) website and saw that development has
147 > moved onto Github[1] (and restarted!). I'm apparently very behind the
148 > times - and perhaps now I should dig out those changes I made and submit
149 > them...
150 >
151 > Glad to see things moving along again.
152 > - P
153 >
154 > [0]: http://gitorious.org/sup/mainline
155 > [1]: https://github.com/sup-heliotrope/sup
156
157 Yup! Dig 'em up. We generally prefer pull requests [0] now a days. Also,
158 we've collected contribution/development resources in the new wiki [1].
159
160
161 I have asked William if he would agree to redirect to/mention the new setup
162 in the old gitorious repo. He gave me access to the sup-team, but I am
163 unfortunately not allowed to make any admin changes to the repository.
164
165
166 Regards, Gaute
167
168
169 [0] https://github.com/sup-heliotrope/sup/pulls
170 [1] https://github.com/sup-heliotrope/sup/wiki/Development
171
172
173 From eg@gaute.vetsj.com Wed Jun 26 12:38:00 2013
174 From: eg@gaute.vetsj.com (Gaute Hope)
175 Date: Wed, 26 Jun 2013 14:38:00 +0200
176 Subject: [sup-talk] Release Sup 0.13.2 and ncursesw-sup 1.3.1.3
177 Message-ID: <1372250076-sup-9668@qwerzila>
178
179 Greetings,
180
181 another release in the 0.13-line. Together with a new release of
182 ncursesw-sup with help from Steven Lawrance Sup should now work on
183 FreeBSD 10 (a wiki page with more info is in the works).
184
185 $ gem install ncursesw-sup
186 $ gem install sup
187
188
189 Thanks to all contributors!
190
191
192 Cheers,
193 Gaute
194
195