* [sup-talk] sup: Fix for an UndefinedMethodError
@ 2013-04-12 18:09 Jonathan Lassoff
2013-04-12 18:46 ` Steven Hum
2013-04-12 19:46 ` Hamish D
0 siblings, 2 replies; 30+ messages in thread
From: Jonathan Lassoff @ 2013-04-12 18:09 UTC (permalink / raw)
To: sup-talk, William Morgan
I kept hitting this bug that was driving me nuts.
While editing a message, I'd go to add a recipient that I don't usually email.
So, I'd leave my draft in a buffer, find a mail from them, and go to
update their contact, only to get hit with an undefined method error.
This seems to get triggered if you ever set a new alias for a contact
that already exists in the contacts list.
I made a fix on my branch on gitorious.
https://gitorious.org/~jofathan/sup/jofathan-sup/commit/7754799bc186833371c7839142270fe65b942ee6
Is anyone still monitoring the sup/mainline repo on gitorious?
William Morgan? Are you still active with sup? Does sup need a new maintainer?
I still use sup every day for my work email, and its my favorite client ever.
Maybe it would be useful to have a sup hackers meetup in San Francisco?
The crash was like:
[Fri Apr 12 10:04:55 -0700 2013] ERROR: oh crap, an exception
----------------------------------------------------------------
I'm very sorry. It seems that an error occurred in Sup. Please
accept my sincere apologies. Please submit the contents of
/home/jof/.sup/exception-log.txt and a brief report of the
circumstances to http://masanjin.net/sup-bugs/ so that I might
address this problem. Thank you!
Sincerely,
William
----------------------------------------------------------------
--- NoMethodError from thread: main
undefined method `email' for "THE_PERSONS_ALIAS_NAME":String
/usr/lib/ruby/1.8/sup/contact.rb:33:in `update_alias'
(eval):1:in `send'
(eval):1:in `update_alias'
/usr/lib/ruby/1.8/sup/modes/contact-list-mode.rb:13:in `alias_contact'
/usr/lib/ruby/1.8/sup/modes/thread-view-mode.rb:259:in `alias'
/usr/lib/ruby/1.8/sup/mode.rb:59:in `send'
/usr/lib/ruby/1.8/sup/mode.rb:59:in `handle_input'
/usr/lib/ruby/1.8/sup/buffer.rb:278:in `handle_input'
/usr/bin/sup-mail:273
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [sup-talk] sup: Fix for an UndefinedMethodError
2013-04-12 18:09 [sup-talk] sup: Fix for an UndefinedMethodError Jonathan Lassoff
@ 2013-04-12 18:46 ` Steven Hum
2013-04-12 19:46 ` Hamish D
1 sibling, 0 replies; 30+ messages in thread
From: Steven Hum @ 2013-04-12 18:46 UTC (permalink / raw)
To: sup-talk
There was some activity not long ago by some sup users who are trying to
keep sup afloat -- by attempting to rebuild a sup wiki (the original one
had degraded horribly w/o a moderator) and look at current state of sup
(and its forks?).
Unfortunately, I don't have those mailing list messages in my archives
anymore -- I don't hang onto list mail long. But you should be able to
comb the list mail to identify a few people who are trying to spear head
this.
I need to investigate this too.. as I currently use ezyang's fork for
imap maildir handling and would be interested if all the good things
people have added to sup can be rolled back into an official sup master.
Regards,
Steven
Excerpts from Jonathan Lassoff's message of 2013-04-12 14:09:33 -0400:
> I kept hitting this bug that was driving me nuts.
>
> While editing a message, I'd go to add a recipient that I don't usually email.
>
> So, I'd leave my draft in a buffer, find a mail from them, and go to
> update their contact, only to get hit with an undefined method error.
> This seems to get triggered if you ever set a new alias for a contact
> that already exists in the contacts list.
>
> I made a fix on my branch on gitorious.
> https://gitorious.org/~jofathan/sup/jofathan-sup/commit/7754799bc186833371c7839142270fe65b942ee6
>
>
> Is anyone still monitoring the sup/mainline repo on gitorious?
> William Morgan? Are you still active with sup? Does sup need a new maintainer?
>
> I still use sup every day for my work email, and its my favorite client ever.
> Maybe it would be useful to have a sup hackers meetup in San Francisco?
>
>
> The crash was like:
> [Fri Apr 12 10:04:55 -0700 2013] ERROR: oh crap, an exception
> ----------------------------------------------------------------
> I'm very sorry. It seems that an error occurred in Sup. Please
> accept my sincere apologies. Please submit the contents of
> /home/jof/.sup/exception-log.txt and a brief report of the
> circumstances to http://masanjin.net/sup-bugs/ so that I might
> address this problem. Thank you!
>
> Sincerely,
> William
> ----------------------------------------------------------------
> --- NoMethodError from thread: main
> undefined method `email' for "THE_PERSONS_ALIAS_NAME":String
> /usr/lib/ruby/1.8/sup/contact.rb:33:in `update_alias'
> (eval):1:in `send'
> (eval):1:in `update_alias'
> /usr/lib/ruby/1.8/sup/modes/contact-list-mode.rb:13:in `alias_contact'
> /usr/lib/ruby/1.8/sup/modes/thread-view-mode.rb:259:in `alias'
> /usr/lib/ruby/1.8/sup/mode.rb:59:in `send'
> /usr/lib/ruby/1.8/sup/mode.rb:59:in `handle_input'
> /usr/lib/ruby/1.8/sup/buffer.rb:278:in `handle_input'
> /usr/bin/sup-mail:273
--
"Truth or die."
Steven Hum
5 - 28 Gilmour St
Ottawa, ON K2P 0N3
email sdothum@gmail.com
tel 613.237.9058
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [sup-talk] sup: Fix for an UndefinedMethodError
2013-04-12 18:09 [sup-talk] sup: Fix for an UndefinedMethodError Jonathan Lassoff
2013-04-12 18:46 ` Steven Hum
@ 2013-04-12 19:46 ` Hamish D
2013-04-13 9:16 ` Gaute Hope
2013-04-13 10:06 ` Jonathan Lassoff
1 sibling, 2 replies; 30+ messages in thread
From: Hamish D @ 2013-04-12 19:46 UTC (permalink / raw)
To: Jonathan Lassoff, sup-talk
[-- Attachment #1.1: Type: text/plain, Size: 793 bytes --]
We've set up https://github.com/sup-heliotrope/sup
Please feel free to put pull requests up there. And contributions to the
new wiki are also very welcome. We have lots of missing pages ...
https://github.com/sup-heliotrope/sup/wiki
We have emailed William about this but have had no response. So currently
we have no access to publishing gems under the sup name.
As to a meet up, I'm in England so won't be coming to San Francisco :-P
> I'm very sorry. It seems that an error occurred in Sup. Please
> accept my sincere apologies. Please submit the contents of
> /home/jof/.sup/exception-log.txt and a brief report of the
> circumstances to http://masanjin.net/sup-bugs/ so that I might
> address this problem. Thank you!
>
> Sincerely,
> William
We should update this text ...
Hamish
[-- Attachment #1.2: Type: text/html, Size: 1143 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [sup-talk] sup: Fix for an UndefinedMethodError
2013-04-12 19:46 ` Hamish D
@ 2013-04-13 9:16 ` Gaute Hope
2013-04-13 10:09 ` Jonathan Lassoff
2013-04-13 12:49 ` Matthieu Rakotojaona
2013-04-13 10:06 ` Jonathan Lassoff
1 sibling, 2 replies; 30+ messages in thread
From: Gaute Hope @ 2013-04-13 9:16 UTC (permalink / raw)
To: Hamish D; +Cc: Jonathan Lassoff, sup-talk
Hi,
Jonathan: I put your commit into a pull request at:
- https://github.com/sup-heliotrope/sup/pull/19
Also, re-branding and updating to web-references:
- https://github.com/sup-heliotrope/sup/pull/20
any comments on this? You can see the changes I made. I have absolutely
no intentions of stepping on any toes, but this is a suggestion.
It is a pity that the official home page and probably first search
results direct to the abandoned home and gem of sup.
Regards, Gaute
On 12. april 2013 21:46, Hamish D wrote:
> We've set up https://github.com/sup-heliotrope/sup
>
> Please feel free to put pull requests up there. And contributions to the
> new wiki are also very welcome. We have lots of missing pages ...
>
> https://github.com/sup-heliotrope/sup/wiki
>
> We have emailed William about this but have had no response. So currently
> we have no access to publishing gems under the sup name.
>
> As to a meet up, I'm in England so won't be coming to San Francisco :-P
>
>> I'm very sorry. It seems that an error occurred in Sup. Please
>> accept my sincere apologies. Please submit the contents of
>> /home/jof/.sup/exception-log.txt and a brief report of the
>> circumstances to http://masanjin.net/sup-bugs/ so that I might
>> address this problem. Thank you!
>>
>> Sincerely,
>> William
>
> We should update this text ...
>
> Hamish
>
>
>
> _______________________________________________
> sup-talk mailing list
> sup-talk@rubyforge.org
> http://rubyforge.org/mailman/listinfo/sup-talk
>
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [sup-talk] sup: Fix for an UndefinedMethodError
2013-04-12 19:46 ` Hamish D
2013-04-13 9:16 ` Gaute Hope
@ 2013-04-13 10:06 ` Jonathan Lassoff
1 sibling, 0 replies; 30+ messages in thread
From: Jonathan Lassoff @ 2013-04-13 10:06 UTC (permalink / raw)
To: Hamish D; +Cc: sup-talk
On Fri, Apr 12, 2013 at 12:46 PM, Hamish D <dmishd@gmail.com> wrote:
> We've set up https://github.com/sup-heliotrope/sup
>
> Please feel free to put pull requests up there. And contributions to the new
> wiki are also very welcome. We have lots of missing pages ...
>
> https://github.com/sup-heliotrope/sup/wiki
Hey -- that's a most excellent place to put a wiki up. Glad to find
where the action's at.
> We have emailed William about this but have had no response. So currently we
> have no access to publishing gems under the sup name.
>
> As to a meet up, I'm in England so won't be coming to San Francisco :-P
Oh no worries, I just mention it because I know WIlliam is from
somewhere around here. I think he's working in SF now.
>> I'm very sorry. It seems that an error occurred in Sup. Please
>> accept my sincere apologies. Please submit the contents of
>> /home/jof/.sup/exception-log.txt and a brief report of the
>> circumstances to http://masanjin.net/sup-bugs/ so that I might
>> address this problem. Thank you!
>>
>> Sincerely,
>> William
>
> We should update this text ...
>
> Hamish
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [sup-talk] sup: Fix for an UndefinedMethodError
2013-04-13 9:16 ` Gaute Hope
@ 2013-04-13 10:09 ` Jonathan Lassoff
2013-04-13 13:17 ` Gaute Hope
2013-04-13 12:49 ` Matthieu Rakotojaona
1 sibling, 1 reply; 30+ messages in thread
From: Jonathan Lassoff @ 2013-04-13 10:09 UTC (permalink / raw)
To: Gaute Hope; +Cc: Hamish D, sup-talk
On Sat, Apr 13, 2013 at 2:16 AM, Gaute Hope <eg@gaute.vetsj.com> wrote:
> Hi,
>
> Jonathan: I put your commit into a pull request at:
> - https://github.com/sup-heliotrope/sup/pull/19
>
> Also, re-branding and updating to web-references:
> - https://github.com/sup-heliotrope/sup/pull/20
>
> any comments on this? You can see the changes I made. I have absolutely
> no intentions of stepping on any toes, but this is a suggestion.
No, thank you very much! That looks great!
> It is a pity that the official home page and probably first search
> results direct to the abandoned home and gem of sup.
It is too bad. Hopefully William could hand off access or at least
push updates somehow.
If not, maybe we could stand up another domain pointing to github pages?
Looks like supmua.org and supm.ua are available. :p
--j
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [sup-talk] sup: Fix for an UndefinedMethodError
2013-04-13 9:16 ` Gaute Hope
2013-04-13 10:09 ` Jonathan Lassoff
@ 2013-04-13 12:49 ` Matthieu Rakotojaona
2013-04-13 13:29 ` Gaute Hope
1 sibling, 1 reply; 30+ messages in thread
From: Matthieu Rakotojaona @ 2013-04-13 12:49 UTC (permalink / raw)
To: sup-talk
On 04/13, Gaute Hope wrote:
> Hi,
>
> Jonathan: I put your commit into a pull request at:
> - https://github.com/sup-heliotrope/sup/pull/19
>
> Also, re-branding and updating to web-references:
> - https://github.com/sup-heliotrope/sup/pull/20
>
> any comments on this? You can see the changes I made. I have absolutely
> no intentions of stepping on any toes, but this is a suggestion.
>
> It is a pity that the official home page and probably first search
> results direct to the abandoned home and gem of sup.
>
> Regards, Gaute
I guess it's also the occasion to think about the mailing list. I guess
no one has the rights on this one ? I don't see anything in github for
this functionality.
--
Matthieu Rakotojaona
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [sup-talk] sup: Fix for an UndefinedMethodError
2013-04-13 10:09 ` Jonathan Lassoff
@ 2013-04-13 13:17 ` Gaute Hope
2013-04-13 16:35 ` Jonathan Lassoff
0 siblings, 1 reply; 30+ messages in thread
From: Gaute Hope @ 2013-04-13 13:17 UTC (permalink / raw)
To: Jonathan Lassoff; +Cc: Hamish D, sup-talk
On la. 13. april 2013 kl. 12.09 +0200, Jonathan Lassoff wrote:
> On Sat, Apr 13, 2013 at 2:16 AM, Gaute Hope <eg@gaute.vetsj.com> wrote:
>> Hi,
>>
>> Jonathan: I put your commit into a pull request at:
>> - https://github.com/sup-heliotrope/sup/pull/19
>>
>> Also, re-branding and updating to web-references:
>> - https://github.com/sup-heliotrope/sup/pull/20
>>
>> any comments on this? You can see the changes I made. I have absolutely
>> no intentions of stepping on any toes, but this is a suggestion.
>
> No, thank you very much! That looks great!
>
>> It is a pity that the official home page and probably first search
>> results direct to the abandoned home and gem of sup.
>
> It is too bad. Hopefully William could hand off access or at least
> push updates somehow.
>
> If not, maybe we could stand up another domain pointing to github pages?
> Looks like supmua.org and supm.ua are available. :p
>
> --j
Yeah.. I think some web page is pretty essential, perhaps just the
standard github-pages domain for a start. Anyone feel up for the task,
I'd be happy to add you to the github-organization.
Regards, Gaute
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [sup-talk] sup: Fix for an UndefinedMethodError
2013-04-13 12:49 ` Matthieu Rakotojaona
@ 2013-04-13 13:29 ` Gaute Hope
2013-04-13 15:42 ` Steven Hum
0 siblings, 1 reply; 30+ messages in thread
From: Gaute Hope @ 2013-04-13 13:29 UTC (permalink / raw)
To: Matthieu Rakotojaona; +Cc: sup-talk
On 13. april 2013 14:49, Matthieu Rakotojaona wrote:
> I guess it's also the occasion to think about the mailing list. I guess
> no one has the rights on this one ? I don't see anything in github for
> this functionality.
Yup - maybe its time for 'sup2' - from rubyforge:
http://rubyforge.org/docman/view.php/5/460/faq.html#abandoned
Project xyz seems to be abandoned. Can you pass it to me?
This comes up occasionally - a well-named or positioned project gets
started, then the project admin falls out of sight and can't be reached.
Patches pile up, people start wondering what's going on, and it seems a
shame to lose the project name by forking it. So someone will ask if we
as RubyForge admins will pass over control of the project to them.
We really, really, hesitate to transfer admin privileges from one person
to another, even if the original admin has completely disappeared. I
suspect there are legal complications, and we don't have the budget to
deal with those. Furthermore, suppose the original admin has been off on
furlough for a year and comes back to find that his project has been
moved away from him. Not a pleasant situation.
In situations where the project admin can't be reached for a long time
and folks want to move forward, I suggest forking the project. You're
welcome to host a xyz2 version of project xyz on RubyForge, and if the
original admin ever shows up again and wants to hand over the project to
you, we can help facilitate that.
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [sup-talk] sup: Fix for an UndefinedMethodError
2013-04-13 13:29 ` Gaute Hope
@ 2013-04-13 15:42 ` Steven Hum
0 siblings, 0 replies; 30+ messages in thread
From: Steven Hum @ 2013-04-13 15:42 UTC (permalink / raw)
To: sup-talk
I was thinking the same, that it may be time for a sup2 repository.
This is very premature, but are there any thoughts to integrate some of
the work done in the sup forks. I am thinking in particular of the imap
work ezyang did -- I adopted his fork as he seemed to be the most active
with regards to imap folder handling, notably propagating updates.
It would be nice to consolidate the features many of these forks
addressed.. though, I have no idea how this can be easily facilitated.
Regards,
Steven
Excerpts from Gaute Hope's message of 2013-04-13 09:29:08 -0400:
> On 13. april 2013 14:49, Matthieu Rakotojaona wrote:
> > I guess it's also the occasion to think about the mailing list. I guess
> > no one has the rights on this one ? I don't see anything in github for
> > this functionality.
>
>
> Yup - maybe its time for 'sup2' - from rubyforge:
>
> http://rubyforge.org/docman/view.php/5/460/faq.html#abandoned
>
> Project xyz seems to be abandoned. Can you pass it to me?
>
> This comes up occasionally - a well-named or positioned project gets
> started, then the project admin falls out of sight and can't be reached.
> Patches pile up, people start wondering what's going on, and it seems a
> shame to lose the project name by forking it. So someone will ask if we
> as RubyForge admins will pass over control of the project to them.
>
> We really, really, hesitate to transfer admin privileges from one person
> to another, even if the original admin has completely disappeared. I
> suspect there are legal complications, and we don't have the budget to
> deal with those. Furthermore, suppose the original admin has been off on
> furlough for a year and comes back to find that his project has been
> moved away from him. Not a pleasant situation.
>
> In situations where the project admin can't be reached for a long time
> and folks want to move forward, I suggest forking the project. You're
> welcome to host a xyz2 version of project xyz on RubyForge, and if the
> original admin ever shows up again and wants to hand over the project to
> you, we can help facilitate that.
--
"Truth or die."
Steven Hum
5 - 28 Gilmour St
Ottawa, ON K2P 0N3
email sdothum@gmail.com
tel 613.237.9058
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [sup-talk] sup: Fix for an UndefinedMethodError
2013-04-13 13:17 ` Gaute Hope
@ 2013-04-13 16:35 ` Jonathan Lassoff
2013-04-13 17:14 ` Gaute Hope
0 siblings, 1 reply; 30+ messages in thread
From: Jonathan Lassoff @ 2013-04-13 16:35 UTC (permalink / raw)
To: Gaute Hope; +Cc: Hamish D, sup-talk
On Sat, Apr 13, 2013 at 6:17 AM, Gaute Hope <eg@gaute.vetsj.com> wrote:
> On la. 13. april 2013 kl. 12.09 +0200, Jonathan Lassoff wrote:
>> On Sat, Apr 13, 2013 at 2:16 AM, Gaute Hope <eg@gaute.vetsj.com> wrote:
>>> Hi,
>>>
>>> Jonathan: I put your commit into a pull request at:
>>> - https://github.com/sup-heliotrope/sup/pull/19
>>>
>>> Also, re-branding and updating to web-references:
>>> - https://github.com/sup-heliotrope/sup/pull/20
>>>
>>> any comments on this? You can see the changes I made. I have absolutely
>>> no intentions of stepping on any toes, but this is a suggestion.
>>
>> No, thank you very much! That looks great!
>>
>>> It is a pity that the official home page and probably first search
>>> results direct to the abandoned home and gem of sup.
>>
>> It is too bad. Hopefully William could hand off access or at least
>> push updates somehow.
>>
>> If not, maybe we could stand up another domain pointing to github pages?
>> Looks like supmua.org and supm.ua are available. :p
>>
>> --j
>
> Yeah.. I think some web page is pretty essential, perhaps just the
> standard github-pages domain for a start. Anyone feel up for the task,
> I'd be happy to add you to the github-organization.
Agreed. I snagged supmua.org for a year, and have it pointing at
sup-heliotrope.github.io for pages.
Stick me on the org, and I'll see about getting a simple site started.
Cheers,
jof
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [sup-talk] sup: Fix for an UndefinedMethodError
2013-04-13 16:35 ` Jonathan Lassoff
@ 2013-04-13 17:14 ` Gaute Hope
2013-04-13 17:37 ` Gaute Hope
2013-04-13 19:15 ` Jonathan Lassoff
0 siblings, 2 replies; 30+ messages in thread
From: Gaute Hope @ 2013-04-13 17:14 UTC (permalink / raw)
To: Jonathan Lassoff; +Cc: Hamish D, sup-talk
On 13. april 2013 18:35, Jonathan Lassoff wrote:
> On Sat, Apr 13, 2013 at 6:17 AM, Gaute Hope <eg@gaute.vetsj.com> wrote:
>> On la. 13. april 2013 kl. 12.09 +0200, Jonathan Lassoff wrote:
>>> On Sat, Apr 13, 2013 at 2:16 AM, Gaute Hope <eg@gaute.vetsj.com> wrote:
>>>> Hi,
>>>>
>>>> Jonathan: I put your commit into a pull request at:
>>>> - https://github.com/sup-heliotrope/sup/pull/19
>>>>
>>>> Also, re-branding and updating to web-references:
>>>> - https://github.com/sup-heliotrope/sup/pull/20
>>>>
>>>> any comments on this? You can see the changes I made. I have absolutely
>>>> no intentions of stepping on any toes, but this is a suggestion.
>>>
>>> No, thank you very much! That looks great!
>>>
>>>> It is a pity that the official home page and probably first search
>>>> results direct to the abandoned home and gem of sup.
>>>
>>> It is too bad. Hopefully William could hand off access or at least
>>> push updates somehow.
>>>
>>> If not, maybe we could stand up another domain pointing to github pages?
>>> Looks like supmua.org and supm.ua are available. :p
>>>
>>> --j
>>
>> Yeah.. I think some web page is pretty essential, perhaps just the
>> standard github-pages domain for a start. Anyone feel up for the task,
>> I'd be happy to add you to the github-organization.
>
> Agreed. I snagged supmua.org for a year, and have it pointing at
> sup-heliotrope.github.io for pages.
>
> Stick me on the org, and I'll see about getting a simple site started.
Nice. You're on.
Cheers, Gaute
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [sup-talk] sup: Fix for an UndefinedMethodError
2013-04-13 17:14 ` Gaute Hope
@ 2013-04-13 17:37 ` Gaute Hope
2013-04-13 19:19 ` Jonathan Lassoff
` (2 more replies)
2013-04-13 19:15 ` Jonathan Lassoff
1 sibling, 3 replies; 30+ messages in thread
From: Gaute Hope @ 2013-04-13 17:37 UTC (permalink / raw)
To: Jonathan Lassoff; +Cc: Hamish D, sup-talk, Sup developer discussion
If we go sup2 I would suggest the following plan:
- Release the best we can get with the current code for 1.9.3 as a last
community release of sup-0.12, say.. sup-0.13.
For sup2:
- Fork a new repo: sup2
- Go for Mail in stead of RMail (index breakage)
- Go for only Psych (config breakage), requires psych gem in 1.8
- Integrate the IMAP / label sync back stuff (personally this is what I
miss the most)
- Go for ruby 2.0.0 and maybe 1.8
- Get rid of all dependencies that are abandoned or deprecated (ncurses
gem..)
- Try to do tests on most stuff for different encodings
- Try to get UTF-8 / encoding right
- Move all the rest of the infrastructure to something the project is in
control of
Would be very nice:
- Index migration
- Config migration
For the web page (eventually):
- note about the original project
- note about the last sup-0.13 release
- wiki and project page for sup2
This plan more or less holds whether we go sup2 or not, but I think it
is easier to get rid of the hopeless dependencies.
@sup-devel readers: discussion is currently at sup-talk, please send any
responses there.
Regards, Gaute
On 13. april 2013 19:14, Gaute Hope wrote:
>
>
> On 13. april 2013 18:35, Jonathan Lassoff wrote:
>> On Sat, Apr 13, 2013 at 6:17 AM, Gaute Hope <eg@gaute.vetsj.com> wrote:
>>> On la. 13. april 2013 kl. 12.09 +0200, Jonathan Lassoff wrote:
>>>> On Sat, Apr 13, 2013 at 2:16 AM, Gaute Hope <eg@gaute.vetsj.com> wrote:
>>>>> Hi,
>>>>>
>>>>> Jonathan: I put your commit into a pull request at:
>>>>> - https://github.com/sup-heliotrope/sup/pull/19
>>>>>
>>>>> Also, re-branding and updating to web-references:
>>>>> - https://github.com/sup-heliotrope/sup/pull/20
>>>>>
>>>>> any comments on this? You can see the changes I made. I have absolutely
>>>>> no intentions of stepping on any toes, but this is a suggestion.
>>>>
>>>> No, thank you very much! That looks great!
>>>>
>>>>> It is a pity that the official home page and probably first search
>>>>> results direct to the abandoned home and gem of sup.
>>>>
>>>> It is too bad. Hopefully William could hand off access or at least
>>>> push updates somehow.
>>>>
>>>> If not, maybe we could stand up another domain pointing to github pages?
>>>> Looks like supmua.org and supm.ua are available. :p
>>>>
>>>> --j
>>>
>>> Yeah.. I think some web page is pretty essential, perhaps just the
>>> standard github-pages domain for a start. Anyone feel up for the task,
>>> I'd be happy to add you to the github-organization.
>>
>> Agreed. I snagged supmua.org for a year, and have it pointing at
>> sup-heliotrope.github.io for pages.
>>
>> Stick me on the org, and I'll see about getting a simple site started.
>
> Nice. You're on.
>
> Cheers, Gaute
>
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [sup-talk] sup: Fix for an UndefinedMethodError
2013-04-13 17:14 ` Gaute Hope
2013-04-13 17:37 ` Gaute Hope
@ 2013-04-13 19:15 ` Jonathan Lassoff
2013-04-13 22:20 ` Gaute Hope
1 sibling, 1 reply; 30+ messages in thread
From: Jonathan Lassoff @ 2013-04-13 19:15 UTC (permalink / raw)
To: Gaute Hope; +Cc: Hamish D, sup-talk
http://supmua.org/
Just tossed this, up but it's mostly stuff from the old rubyforge page.
On Sat, Apr 13, 2013 at 10:14 AM, Gaute Hope <eg@gaute.vetsj.com> wrote:
>
>
> On 13. april 2013 18:35, Jonathan Lassoff wrote:
>> On Sat, Apr 13, 2013 at 6:17 AM, Gaute Hope <eg@gaute.vetsj.com> wrote:
>>> On la. 13. april 2013 kl. 12.09 +0200, Jonathan Lassoff wrote:
>>>> On Sat, Apr 13, 2013 at 2:16 AM, Gaute Hope <eg@gaute.vetsj.com> wrote:
>>>>> Hi,
>>>>>
>>>>> Jonathan: I put your commit into a pull request at:
>>>>> - https://github.com/sup-heliotrope/sup/pull/19
>>>>>
>>>>> Also, re-branding and updating to web-references:
>>>>> - https://github.com/sup-heliotrope/sup/pull/20
>>>>>
>>>>> any comments on this? You can see the changes I made. I have absolutely
>>>>> no intentions of stepping on any toes, but this is a suggestion.
>>>>
>>>> No, thank you very much! That looks great!
>>>>
>>>>> It is a pity that the official home page and probably first search
>>>>> results direct to the abandoned home and gem of sup.
>>>>
>>>> It is too bad. Hopefully William could hand off access or at least
>>>> push updates somehow.
>>>>
>>>> If not, maybe we could stand up another domain pointing to github pages?
>>>> Looks like supmua.org and supm.ua are available. :p
>>>>
>>>> --j
>>>
>>> Yeah.. I think some web page is pretty essential, perhaps just the
>>> standard github-pages domain for a start. Anyone feel up for the task,
>>> I'd be happy to add you to the github-organization.
>>
>> Agreed. I snagged supmua.org for a year, and have it pointing at
>> sup-heliotrope.github.io for pages.
>>
>> Stick me on the org, and I'll see about getting a simple site started.
>
> Nice. You're on.
>
> Cheers, Gaute
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [sup-talk] sup: Fix for an UndefinedMethodError
2013-04-13 17:37 ` Gaute Hope
@ 2013-04-13 19:19 ` Jonathan Lassoff
2013-04-13 20:48 ` Jonathan Lassoff
2013-04-14 11:31 ` [sup-devel] " Eric Weikl
2013-04-14 17:45 ` [sup-talk] sup: Fix for an UndefinedMethodError Hamish D
2 siblings, 1 reply; 30+ messages in thread
From: Jonathan Lassoff @ 2013-04-13 19:19 UTC (permalink / raw)
To: Gaute Hope; +Cc: Hamish D, sup-talk, Sup developer discussion
On Sat, Apr 13, 2013 at 10:37 AM, Gaute Hope <eg@gaute.vetsj.com> wrote:
> If we go sup2 I would suggest the following plan:
>
> - Release the best we can get with the current code for 1.9.3 as a last
> community release of sup-0.12, say.. sup-0.13.
>
> For sup2:
> - Fork a new repo: sup2
> - Go for Mail in stead of RMail (index breakage)
> - Go for only Psych (config breakage), requires psych gem in 1.8
> - Integrate the IMAP / label sync back stuff (personally this is what I
> miss the most)
> - Go for ruby 2.0.0 and maybe 1.8
> - Get rid of all dependencies that are abandoned or deprecated (ncurses
> gem..)
And target ncursesw?
> - Try to do tests on most stuff for different encodings
> - Try to get UTF-8 / encoding right
> - Move all the rest of the infrastructure to something the project is in
> control of
>
> Would be very nice:
> - Index migration
> - Config migration
>
> For the web page (eventually):
> - note about the original project
> - note about the last sup-0.13 release
> - wiki and project page for sup2
>
> This plan more or less holds whether we go sup2 or not, but I think it
> is easier to get rid of the hopeless dependencies.
I agree that it's worth it to drop unmaintained dependencies and just
fix what breaks.
It would be unfortunate to have to fork the project and make a
different name. I wonder if Morgan has lost interest or is just busy
with other things.
Cheers,
jof
> @sup-devel readers: discussion is currently at sup-talk, please send any
> responses there.
>
> Regards, Gaute
>
> On 13. april 2013 19:14, Gaute Hope wrote:
>>
>>
>> On 13. april 2013 18:35, Jonathan Lassoff wrote:
>>> On Sat, Apr 13, 2013 at 6:17 AM, Gaute Hope <eg@gaute.vetsj.com> wrote:
>>>> On la. 13. april 2013 kl. 12.09 +0200, Jonathan Lassoff wrote:
>>>>> On Sat, Apr 13, 2013 at 2:16 AM, Gaute Hope <eg@gaute.vetsj.com> wrote:
>>>>>> Hi,
>>>>>>
>>>>>> Jonathan: I put your commit into a pull request at:
>>>>>> - https://github.com/sup-heliotrope/sup/pull/19
>>>>>>
>>>>>> Also, re-branding and updating to web-references:
>>>>>> - https://github.com/sup-heliotrope/sup/pull/20
>>>>>>
>>>>>> any comments on this? You can see the changes I made. I have absolutely
>>>>>> no intentions of stepping on any toes, but this is a suggestion.
>>>>>
>>>>> No, thank you very much! That looks great!
>>>>>
>>>>>> It is a pity that the official home page and probably first search
>>>>>> results direct to the abandoned home and gem of sup.
>>>>>
>>>>> It is too bad. Hopefully William could hand off access or at least
>>>>> push updates somehow.
>>>>>
>>>>> If not, maybe we could stand up another domain pointing to github pages?
>>>>> Looks like supmua.org and supm.ua are available. :p
>>>>>
>>>>> --j
>>>>
>>>> Yeah.. I think some web page is pretty essential, perhaps just the
>>>> standard github-pages domain for a start. Anyone feel up for the task,
>>>> I'd be happy to add you to the github-organization.
>>>
>>> Agreed. I snagged supmua.org for a year, and have it pointing at
>>> sup-heliotrope.github.io for pages.
>>>
>>> Stick me on the org, and I'll see about getting a simple site started.
>>
>> Nice. You're on.
>>
>> Cheers, Gaute
>>
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [sup-talk] sup: Fix for an UndefinedMethodError
2013-04-13 19:19 ` Jonathan Lassoff
@ 2013-04-13 20:48 ` Jonathan Lassoff
2013-04-13 22:17 ` Gaute Hope
0 siblings, 1 reply; 30+ messages in thread
From: Jonathan Lassoff @ 2013-04-13 20:48 UTC (permalink / raw)
To: Gaute Hope; +Cc: Hamish D, sup-talk, Sup developer discussion
Maybe William can help out?
https://twitter.com/wm/status/323175493367119873
On Sat, Apr 13, 2013 at 12:19 PM, Jonathan Lassoff <jof@thejof.com> wrote:
> On Sat, Apr 13, 2013 at 10:37 AM, Gaute Hope <eg@gaute.vetsj.com> wrote:
>> If we go sup2 I would suggest the following plan:
>>
>> - Release the best we can get with the current code for 1.9.3 as a last
>> community release of sup-0.12, say.. sup-0.13.
>>
>> For sup2:
>> - Fork a new repo: sup2
>> - Go for Mail in stead of RMail (index breakage)
>> - Go for only Psych (config breakage), requires psych gem in 1.8
>> - Integrate the IMAP / label sync back stuff (personally this is what I
>> miss the most)
>> - Go for ruby 2.0.0 and maybe 1.8
>> - Get rid of all dependencies that are abandoned or deprecated (ncurses
>> gem..)
>
> And target ncursesw?
>
>> - Try to do tests on most stuff for different encodings
>> - Try to get UTF-8 / encoding right
>> - Move all the rest of the infrastructure to something the project is in
>> control of
>>
>> Would be very nice:
>> - Index migration
>> - Config migration
>>
>> For the web page (eventually):
>> - note about the original project
>> - note about the last sup-0.13 release
>> - wiki and project page for sup2
>>
>> This plan more or less holds whether we go sup2 or not, but I think it
>> is easier to get rid of the hopeless dependencies.
>
> I agree that it's worth it to drop unmaintained dependencies and just
> fix what breaks.
> It would be unfortunate to have to fork the project and make a
> different name. I wonder if Morgan has lost interest or is just busy
> with other things.
>
> Cheers,
> jof
>> @sup-devel readers: discussion is currently at sup-talk, please send any
>> responses there.
>>
>> Regards, Gaute
>>
>> On 13. april 2013 19:14, Gaute Hope wrote:
>>>
>>>
>>> On 13. april 2013 18:35, Jonathan Lassoff wrote:
>>>> On Sat, Apr 13, 2013 at 6:17 AM, Gaute Hope <eg@gaute.vetsj.com> wrote:
>>>>> On la. 13. april 2013 kl. 12.09 +0200, Jonathan Lassoff wrote:
>>>>>> On Sat, Apr 13, 2013 at 2:16 AM, Gaute Hope <eg@gaute.vetsj.com> wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> Jonathan: I put your commit into a pull request at:
>>>>>>> - https://github.com/sup-heliotrope/sup/pull/19
>>>>>>>
>>>>>>> Also, re-branding and updating to web-references:
>>>>>>> - https://github.com/sup-heliotrope/sup/pull/20
>>>>>>>
>>>>>>> any comments on this? You can see the changes I made. I have absolutely
>>>>>>> no intentions of stepping on any toes, but this is a suggestion.
>>>>>>
>>>>>> No, thank you very much! That looks great!
>>>>>>
>>>>>>> It is a pity that the official home page and probably first search
>>>>>>> results direct to the abandoned home and gem of sup.
>>>>>>
>>>>>> It is too bad. Hopefully William could hand off access or at least
>>>>>> push updates somehow.
>>>>>>
>>>>>> If not, maybe we could stand up another domain pointing to github pages?
>>>>>> Looks like supmua.org and supm.ua are available. :p
>>>>>>
>>>>>> --j
>>>>>
>>>>> Yeah.. I think some web page is pretty essential, perhaps just the
>>>>> standard github-pages domain for a start. Anyone feel up for the task,
>>>>> I'd be happy to add you to the github-organization.
>>>>
>>>> Agreed. I snagged supmua.org for a year, and have it pointing at
>>>> sup-heliotrope.github.io for pages.
>>>>
>>>> Stick me on the org, and I'll see about getting a simple site started.
>>>
>>> Nice. You're on.
>>>
>>> Cheers, Gaute
>>>
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [sup-talk] sup: Fix for an UndefinedMethodError
2013-04-13 20:48 ` Jonathan Lassoff
@ 2013-04-13 22:17 ` Gaute Hope
0 siblings, 0 replies; 30+ messages in thread
From: Gaute Hope @ 2013-04-13 22:17 UTC (permalink / raw)
To: Jonathan Lassoff; +Cc: Hamish D, sup-talk, Sup developer discussion
On la. 13. april 2013 kl. 22.48 +0200, Jonathan Lassoff wrote:
> Maybe William can help out?
> https://twitter.com/wm/status/323175493367119873
That would be the best ;)
But I still think we need to get rid of the deprecated and abandoned
stuff.
- gaute
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [sup-talk] sup: Fix for an UndefinedMethodError
2013-04-13 19:15 ` Jonathan Lassoff
@ 2013-04-13 22:20 ` Gaute Hope
0 siblings, 0 replies; 30+ messages in thread
From: Gaute Hope @ 2013-04-13 22:20 UTC (permalink / raw)
To: Jonathan Lassoff; +Cc: Hamish D, sup-talk
On 13. april 2013 21:15, Jonathan Lassoff wrote:
> http://supmua.org/
>
> Just tossed this, up but it's mostly stuff from the old rubyforge page.
Thats a good start, nice work!
- gaute
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [sup-devel] [sup-talk] sup: Fix for an UndefinedMethodError
2013-04-13 17:37 ` Gaute Hope
2013-04-13 19:19 ` Jonathan Lassoff
@ 2013-04-14 11:31 ` Eric Weikl
2013-04-14 12:05 ` Gaute Hope
2013-04-14 17:45 ` [sup-talk] sup: Fix for an UndefinedMethodError Hamish D
2 siblings, 1 reply; 30+ messages in thread
From: Eric Weikl @ 2013-04-14 11:31 UTC (permalink / raw)
To: Gaute Hope; +Cc: sup-talk
Hi Gaute,
That sounds like a plan of action :-)
Excerpts from Gaute Hope's message of 2013-04-13 19:37:01 +0200:
> - Go for Mail in stead of RMail (index breakage)
Is this related to getting rid of Iconv for Ruby 2.0.0, or is it a
separate issue? Otherwise, I would favor lumping it in the same release
together with IMAP syncback, since both require a migration step by the
user.
> - Integrate the IMAP / label sync back stuff (personally this is what I
> miss the most)
I've been using the imap syncback code by Damien Leone from ezyang's
branch for quite a while now (> 1 year) without any issues. It should be
fairly easy to cherry-pick the relevant commits into the development
branch.
> - Get rid of all dependencies that are abandoned or deprecated (ncurses
> gem..)
+1 I'd also add deleting all unused code and other stuff (server code,
website, Redwood protocol stuff, etc.).
> - Try to do tests on most stuff for different encodings
I thought about adding some functional tests (through the UI or
otherwise), since retrofitting unit tests is probably too much of a pain.
I need to figure out how the parts fit together some more, though.
Do you think that makes sense?
> Would be very nice:
> - Index migration
We could do the index migration like the imap syncback code does - it
recognizes that it wasn't done yet and asks you to run a command-line
tool.
> - Config migration
How exactly will the config change? Possibly it easy to detect via
regular expressions or something?
Cheers,
Eric
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [sup-devel] [sup-talk] sup: Fix for an UndefinedMethodError
2013-04-14 11:31 ` [sup-devel] " Eric Weikl
@ 2013-04-14 12:05 ` Gaute Hope
2013-04-14 17:39 ` Eric Weikl
2013-04-16 20:30 ` [sup-talk] [sup-devel] " Eric Weikl
0 siblings, 2 replies; 30+ messages in thread
From: Gaute Hope @ 2013-04-14 12:05 UTC (permalink / raw)
To: Eric Weikl; +Cc: sup-talk
On 14. april 2013 13:31, Eric Weikl wrote:
> Hi Gaute,
>
> That sounds like a plan of action :-)
>
> Excerpts from Gaute Hope's message of 2013-04-13 19:37:01 +0200:
>> - Go for Mail in stead of RMail (index breakage)
>
> Is this related to getting rid of Iconv for Ruby 2.0.0, or is it a
> separate issue? Otherwise, I would favor lumping it in the same release
> together with IMAP syncback, since both require a migration step by the
> user.
No, RMail and Iconv are separate issues.
Yes, that was my thinking as well - since both config and index need a
migration step. Iconv deprecation should be seamless (syncback as well).
>> - Integrate the IMAP / label sync back stuff (personally this is what I
>> miss the most)
>
> I've been using the imap syncback code by Damien Leone from ezyang's
> branch for quite a while now (> 1 year) without any issues. It should be
> fairly easy to cherry-pick the relevant commits into the development
> branch.
Cool. I would really like to see this in main sup, any other objections?
In my view the main arguments are:
- Manipulating IMAP could mess up user mail (potentially new bugs could
mess up)
- Maintaining this functionality requires some long-term (at least
minor) effort
- It modifies the mail store (could be solved with disabled-by-default)
which I think is a big plus for many
I would suggest creating a official branch for this now, if you are
interested I could add you as commiter or owner.
>> - Get rid of all dependencies that are abandoned or deprecated (ncurses
>> gem..)
>
> +1 I'd also add deleting all unused code and other stuff (server code,
> website, Redwood protocol stuff, etc.).
Yes, you could put Iconv in this category as well.
>> - Try to do tests on most stuff for different encodings
>
> I thought about adding some functional tests (through the UI or
> otherwise), since retrofitting unit tests is probably too much of a pain.
> I need to figure out how the parts fit together some more, though.
> Do you think that makes sense?
>
>> Would be very nice:
>> - Index migration
>
> We could do the index migration like the imap syncback code does - it
> recognizes that it wasn't done yet and asks you to run a command-line
> tool.
Not entirely sure how things are built up, but migration probably
requires to map ids between Mail and RMail (it's going to be messy).
Matthieu had some insight here, see:
https://github.com/sup-heliotrope/sup/issues/22
>> - Config migration
>
> How exactly will the config change? Possibly it easy to detect via
> regular expressions or something?
The YAML output from Syck (deprecated and removed) and Psych is
incompatible. So the old config files are not readable by Psych. An
approach could possibly be: install syck as a gem (if it exists), load
the file with Syck, re-write it with Psych. There exists a Psych gem for
1.8 (which could be conditionally loaded).
Also might be worth taking a look at sup inspired stuff; notmuch /
mutt-kz which I don't think provides the same as sup, but are less buggy
atm.
Cheers,
Gaute
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [sup-devel] [sup-talk] sup: Fix for an UndefinedMethodError
2013-04-14 12:05 ` Gaute Hope
@ 2013-04-14 17:39 ` Eric Weikl
2013-04-16 20:30 ` [sup-talk] [sup-devel] " Eric Weikl
1 sibling, 0 replies; 30+ messages in thread
From: Eric Weikl @ 2013-04-14 17:39 UTC (permalink / raw)
To: Gaute Hope; +Cc: sup-talk
Hi Gaute,
Excerpts from Gaute Hope's message of 2013-04-14 14:05:52 +0200:
> In my view the main arguments are:
>
> - Manipulating IMAP could mess up user mail (potentially new bugs could
> mess up)
Yes. Although my experience was positive until now, this definitely needs
extensive testing (especially when disabled). Volunteers, anyone? :-)
> I would suggest creating a official branch for this now, if you are
> interested I could add you as commiter or owner.
Sure, I can give it a spin.
Cheers,
Eric
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [sup-talk] sup: Fix for an UndefinedMethodError
2013-04-13 17:37 ` Gaute Hope
2013-04-13 19:19 ` Jonathan Lassoff
2013-04-14 11:31 ` [sup-devel] " Eric Weikl
@ 2013-04-14 17:45 ` Hamish D
2013-04-14 22:32 ` Gaute Hope
2013-04-15 11:42 ` Gaute Hope
2 siblings, 2 replies; 30+ messages in thread
From: Hamish D @ 2013-04-14 17:45 UTC (permalink / raw)
To: Gaute Hope, sup-talk
> For sup2:
> - Fork a new repo: sup2
> - Go for Mail in stead of RMail (index breakage)
> - Go for only Psych (config breakage), requires psych gem in 1.8
> - Integrate the IMAP / label sync back stuff (personally this is what I
> miss the most)
> - Go for ruby 2.0.0 and maybe 1.8
> - Get rid of all dependencies that are abandoned or deprecated (ncurses
> gem..)
> - Try to do tests on most stuff for different encodings
> - Try to get UTF-8 / encoding right
> - Move all the rest of the infrastructure to something the project is in
> control of
Another one for the list would be to update the GPG code to use
version 2 of ruby-gpgme - it currently works with ruby-gpgme 1.0.8
Maybe we should move this list to the wiki.
Hamish
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [sup-talk] sup: Fix for an UndefinedMethodError
2013-04-14 17:45 ` [sup-talk] sup: Fix for an UndefinedMethodError Hamish D
@ 2013-04-14 22:32 ` Gaute Hope
2013-04-15 11:42 ` Gaute Hope
1 sibling, 0 replies; 30+ messages in thread
From: Gaute Hope @ 2013-04-14 22:32 UTC (permalink / raw)
To: Hamish D; +Cc: sup-talk
On 14. april 2013 19:45, Hamish D wrote:
>> For sup2:
>> - Fork a new repo: sup2
>> - Go for Mail in stead of RMail (index breakage)
>> - Go for only Psych (config breakage), requires psych gem in 1.8
>> - Integrate the IMAP / label sync back stuff (personally this is what I
>> miss the most)
>> - Go for ruby 2.0.0 and maybe 1.8
>> - Get rid of all dependencies that are abandoned or deprecated (ncurses
>> gem..)
>> - Try to do tests on most stuff for different encodings
>> - Try to get UTF-8 / encoding right
>> - Move all the rest of the infrastructure to something the project is in
>> control of
>
> Another one for the list would be to update the GPG code to use
> version 2 of ruby-gpgme - it currently works with ruby-gpgme 1.0.8
>
> Maybe we should move this list to the wiki.
Definitely: A roadmap for the next sup.
Cheers,
Gaute
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [sup-talk] sup: Fix for an UndefinedMethodError
2013-04-14 17:45 ` [sup-talk] sup: Fix for an UndefinedMethodError Hamish D
2013-04-14 22:32 ` Gaute Hope
@ 2013-04-15 11:42 ` Gaute Hope
1 sibling, 0 replies; 30+ messages in thread
From: Gaute Hope @ 2013-04-15 11:42 UTC (permalink / raw)
To: Hamish D; +Cc: sup-talk
On 14. april 2013 19:45, Hamish D wrote:
>> For sup2:
>> - Fork a new repo: sup2
>> - Go for Mail in stead of RMail (index breakage)
>> - Go for only Psych (config breakage), requires psych gem in 1.8
>> - Integrate the IMAP / label sync back stuff (personally this is what I
>> miss the most)
>> - Go for ruby 2.0.0 and maybe 1.8
>> - Get rid of all dependencies that are abandoned or deprecated (ncurses
>> gem..)
>> - Try to do tests on most stuff for different encodings
>> - Try to get UTF-8 / encoding right
>> - Move all the rest of the infrastructure to something the project is in
>> control of
>
> Another one for the list would be to update the GPG code to use
> version 2 of ruby-gpgme - it currently works with ruby-gpgme 1.0.8
>
> Maybe we should move this list to the wiki.
https://github.com/sup-heliotrope/sup/wiki/Development
Please edit and comment - this was done quickly.
- Gaute
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [sup-talk] [sup-devel] sup: Fix for an UndefinedMethodError
2013-04-14 12:05 ` Gaute Hope
2013-04-14 17:39 ` Eric Weikl
@ 2013-04-16 20:30 ` Eric Weikl
2013-04-16 21:21 ` Matthieu Rakotojaona
` (2 more replies)
1 sibling, 3 replies; 30+ messages in thread
From: Eric Weikl @ 2013-04-16 20:30 UTC (permalink / raw)
To: sup-talk
Hi everyone,
I created a new branch with all the commits from Damien Leone and Edward
Yang related to maildir syncback and put it here:
https://github.com/sup-heliotrope/sup/tree/maildir-sync
I skipped some advanced stuff like Edward's inotify support for now. We
can add that later.
I performed some basic testing, but it would be great if some more people
could give it a try. There's some documentation in the wiki:
https://github.com/sup-heliotrope/sup/wiki/Maildir-Syncback
Cheers,
Eric
Excerpts from Gaute Hope's message of 2013-04-14 14:05:52 +0200:
> Cool. I would really like to see this in main sup, any other
> objections? In my view the main arguments are:
>
> - Manipulating IMAP could mess up user mail (potentially new bugs could
> mess up)
> - Maintaining this functionality requires some long-term (at least
> minor) effort
> - It modifies the mail store (could be solved with disabled-by-default)
> which I think is a big plus for many
>
> I would suggest creating a official branch for this now, if you are
> interested I could add you as commiter or owner.
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [sup-talk] [sup-devel] sup: Fix for an UndefinedMethodError
2013-04-16 20:30 ` [sup-talk] [sup-devel] " Eric Weikl
@ 2013-04-16 21:21 ` Matthieu Rakotojaona
2013-04-17 8:51 ` Gaute Hope
2013-04-17 3:31 ` Steven Hum
2013-08-15 13:22 ` [sup-devel] Is maildir-sync ready for prime time? Eric Weikl
2 siblings, 1 reply; 30+ messages in thread
From: Matthieu Rakotojaona @ 2013-04-16 21:21 UTC (permalink / raw)
To: sup talk
On 04/16, Eric Weikl wrote:
> Hi everyone,
>
> I created a new branch with all the commits from Damien Leone and Edward
> Yang related to maildir syncback and put it here:
>
> https://github.com/sup-heliotrope/sup/tree/maildir-sync
>
> I skipped some advanced stuff like Edward's inotify support for now. We
> can add that later.
>
> I performed some basic testing, but it would be great if some more people
> could give it a try. There's some documentation in the wiki:
>
> https://github.com/sup-heliotrope/sup/wiki/Maildir-Syncback
>
> Cheers,
> Eric
Fantastic. Not being able to sync back was what prevented me from using
it. After much work and discouragement with heliotrope, I will gladly
try this !
On a longer-term note, syncing back to maildir has the limitation that
non-standard flags (i.e labels) will not be handled, unless we start
defining some custom way of storing them or modifying the original
emails, which I highly dislike (this is how mu[0] works). But that's
just something to keep in mind for future times, when we have a stable,
up-to-date sup release. Let's do this ! =]
[0] http://www.djcbsoftware.nl/code/mu/
--
Matthieu Rakotojaona
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [sup-talk] [sup-devel] sup: Fix for an UndefinedMethodError
2013-04-16 20:30 ` [sup-talk] [sup-devel] " Eric Weikl
2013-04-16 21:21 ` Matthieu Rakotojaona
@ 2013-04-17 3:31 ` Steven Hum
2013-08-15 13:22 ` [sup-devel] Is maildir-sync ready for prime time? Eric Weikl
2 siblings, 0 replies; 30+ messages in thread
From: Steven Hum @ 2013-04-17 3:31 UTC (permalink / raw)
To: sup-talk
Beautiful! I will begin using this in place of my copy of ezyang's fork
immediately.
Thanks for all your hard work,
Steven
Excerpts from Eric Weikl's message of 2013-04-16 16:30:26 -0400:
> Hi everyone,
>
> I created a new branch with all the commits from Damien Leone and Edward
> Yang related to maildir syncback and put it here:
>
> https://github.com/sup-heliotrope/sup/tree/maildir-sync
>
> I skipped some advanced stuff like Edward's inotify support for now. We
> can add that later.
>
> I performed some basic testing, but it would be great if some more people
> could give it a try. There's some documentation in the wiki:
>
> https://github.com/sup-heliotrope/sup/wiki/Maildir-Syncback
>
> Cheers,
> Eric
>
> Excerpts from Gaute Hope's message of 2013-04-14 14:05:52 +0200:
> > Cool. I would really like to see this in main sup, any other
> > objections? In my view the main arguments are:
> >
> > - Manipulating IMAP could mess up user mail (potentially new bugs could
> > mess up)
> > - Maintaining this functionality requires some long-term (at least
> > minor) effort
> > - It modifies the mail store (could be solved with disabled-by-default)
> > which I think is a big plus for many
> >
> > I would suggest creating a official branch for this now, if you are
> > interested I could add you as commiter or owner.
--
"Truth or die."
Steven Hum
5 - 28 Gilmour St
Ottawa, ON K2P 0N3
email sdothum@gmail.com
tel 613.237.9058
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [sup-talk] [sup-devel] sup: Fix for an UndefinedMethodError
2013-04-16 21:21 ` Matthieu Rakotojaona
@ 2013-04-17 8:51 ` Gaute Hope
0 siblings, 0 replies; 30+ messages in thread
From: Gaute Hope @ 2013-04-17 8:51 UTC (permalink / raw)
To: Matthieu Rakotojaona; +Cc: sup talk
On 16. april 2013 23:21, Matthieu Rakotojaona wrote:
> On 04/16, Eric Weikl wrote:
>> Hi everyone,
>>
>> I created a new branch with all the commits from Damien Leone and Edward
>> Yang related to maildir syncback and put it here:
>>
>> https://github.com/sup-heliotrope/sup/tree/maildir-sync
>>
>> I skipped some advanced stuff like Edward's inotify support for now. We
>> can add that later.
>>
>> I performed some basic testing, but it would be great if some more people
>> could give it a try. There's some documentation in the wiki:
>>
>> https://github.com/sup-heliotrope/sup/wiki/Maildir-Syncback
>>
>> Cheers,
>> Eric
>
> Fantastic. Not being able to sync back was what prevented me from using
> it. After much work and discouragement with heliotrope, I will gladly
> try this !
>
> On a longer-term note, syncing back to maildir has the limitation that
> non-standard flags (i.e labels) will not be handled, unless we start
> defining some custom way of storing them or modifying the original
> emails, which I highly dislike (this is how mu[0] works). But that's
> just something to keep in mind for future times, when we have a stable,
> up-to-date sup release. Let's do this ! =]
>
> [0] http://www.djcbsoftware.nl/code/mu/
>
Great!
Put up a wikipage for collecting some resources on this:
https://github.com/sup-heliotrope/sup/wiki/Development:-Maildir-syncback
Also a notmuch user created a script for syncing labels to maildir
folders:
https://github.com/altercation/es-bin/blob/master/maildir-notmuch-sync
Cheers, Gaute
^ permalink raw reply [flat|nested] 30+ messages in thread
* [sup-devel] Is maildir-sync ready for prime time?
2013-04-16 20:30 ` [sup-talk] [sup-devel] " Eric Weikl
2013-04-16 21:21 ` Matthieu Rakotojaona
2013-04-17 3:31 ` Steven Hum
@ 2013-08-15 13:22 ` Eric Weikl
2013-08-15 13:35 ` [sup-talk] " Steven Schmeiser
2 siblings, 1 reply; 30+ messages in thread
From: Eric Weikl @ 2013-08-15 13:22 UTC (permalink / raw)
To: sup-talk; +Cc: sup-devel
Hi fellow sup users,
the maildir-sync branch has been hanging around for quite a while. Since
sup 0.14.0 is out now, we could consider merging it into the developer
branch. I've been using the branch continuously and haven't encountered
any problems so far.
Has anyone else tried the branch, or is willing to do so? It would be
great to have some more opinions on it.
Gaute created a corresponding pull request here:
https://github.com/sup-heliotrope/sup/pull/126
Cheers,
Eric
On 04/16/2013 22:30:26, Eric Weikl wrote:
> Hi everyone,
>
> I created a new branch with all the commits from Damien Leone and
> Edward Yang related to maildir syncback and put it here:
>
> https://github.com/sup-heliotrope/sup/tree/maildir-sync
>
> I skipped some advanced stuff like Edward's inotify support for now. We
> can add that later.
>
> I performed some basic testing, but it would be great if some more
> people could give it a try. There's some documentation in the wiki:
>
> https://github.com/sup-heliotrope/sup/wiki/Maildir-Syncback
>
> Cheers,
> Eric
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [sup-talk] Is maildir-sync ready for prime time?
2013-08-15 13:22 ` [sup-devel] Is maildir-sync ready for prime time? Eric Weikl
@ 2013-08-15 13:35 ` Steven Schmeiser
0 siblings, 0 replies; 30+ messages in thread
From: Steven Schmeiser @ 2013-08-15 13:35 UTC (permalink / raw)
To: sup-talk
[-- Attachment #1.1: Type: text/plain, Size: 1294 bytes --]
I've been using the maildir-sync branch for a month or so and have not encountered any problems. I also vote for a merge.
Steve
> Hi fellow sup users,
>
> the maildir-sync branch has been hanging around for quite a while. Since
> sup 0.14.0 is out now, we could consider merging it into the developer
> branch. I've been using the branch continuously and haven't encountered
> any problems so far.
>
> Has anyone else tried the branch, or is willing to do so? It would be
> great to have some more opinions on it.
>
> Gaute created a corresponding pull request here:
> https://github.com/sup-heliotrope/sup/pull/126
>
> Cheers,
> Eric
>
> On 04/16/2013 22:30:26, Eric Weikl wrote:
> > Hi everyone,
> >
> > I created a new branch with all the commits from Damien Leone and
> > Edward Yang related to maildir syncback and put it here:
> >
> > https://github.com/sup-heliotrope/sup/tree/maildir-sync
> >
> > I skipped some advanced stuff like Edward's inotify support for now. We
> > can add that later.
> >
> > I performed some basic testing, but it would be great if some more
> > people could give it a try. There's some documentation in the wiki:
> >
> > https://github.com/sup-heliotrope/sup/wiki/Maildir-Syncback
> >
> > Cheers,
> > Eric
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 841 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 30+ messages in thread
end of thread, other threads:[~2013-08-15 13:43 UTC | newest]
Thread overview: 30+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-04-12 18:09 [sup-talk] sup: Fix for an UndefinedMethodError Jonathan Lassoff
2013-04-12 18:46 ` Steven Hum
2013-04-12 19:46 ` Hamish D
2013-04-13 9:16 ` Gaute Hope
2013-04-13 10:09 ` Jonathan Lassoff
2013-04-13 13:17 ` Gaute Hope
2013-04-13 16:35 ` Jonathan Lassoff
2013-04-13 17:14 ` Gaute Hope
2013-04-13 17:37 ` Gaute Hope
2013-04-13 19:19 ` Jonathan Lassoff
2013-04-13 20:48 ` Jonathan Lassoff
2013-04-13 22:17 ` Gaute Hope
2013-04-14 11:31 ` [sup-devel] " Eric Weikl
2013-04-14 12:05 ` Gaute Hope
2013-04-14 17:39 ` Eric Weikl
2013-04-16 20:30 ` [sup-talk] [sup-devel] " Eric Weikl
2013-04-16 21:21 ` Matthieu Rakotojaona
2013-04-17 8:51 ` Gaute Hope
2013-04-17 3:31 ` Steven Hum
2013-08-15 13:22 ` [sup-devel] Is maildir-sync ready for prime time? Eric Weikl
2013-08-15 13:35 ` [sup-talk] " Steven Schmeiser
2013-04-14 17:45 ` [sup-talk] sup: Fix for an UndefinedMethodError Hamish D
2013-04-14 22:32 ` Gaute Hope
2013-04-15 11:42 ` Gaute Hope
2013-04-13 19:15 ` Jonathan Lassoff
2013-04-13 22:20 ` Gaute Hope
2013-04-13 12:49 ` Matthieu Rakotojaona
2013-04-13 13:29 ` Gaute Hope
2013-04-13 15:42 ` Steven Hum
2013-04-13 10:06 ` Jonathan Lassoff
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox