Subject: Re: [sup-talk] sup: Fix for an UndefinedMethodError

From: Hamish D <[email-masked]>
Date: Sun, 14 Apr 2013 18:45:57 +0100

> 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

---

From: Gaute Hope <[email-masked]>
Date: Sun, 14 Apr 2013 00:20:55 +0200

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

---

From: Matthieu Rakotojaona <[email-masked]>
Date: Tue, 16 Apr 2013 23:21:45 +0200

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
[email-masked]
http://rubyforge.org/mailman/listinfo/sup-talk

---

From: Jonathan Lassoff <[email-masked]>
Date: Sat, 13 Apr 2013 03:06:21 -0700

On Fri, Apr 12, 2013 at 12:46 PM, Hamish D <[email-masked]> 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

---

From: Steven Hum <[email-masked]>
Date: Fri, 12 Apr 2013 14:46:59 -0400

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
> ----------------------------------------------------------------
> ----------------------------------------------------------------
> --- 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 [email-masked]  
tel 613.237.9058

---

From: Matthieu Rakotojaona <[email-masked]>
Date: Sat, 13 Apr 2013 14:49:46 +0200

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.

---

From: Gaute Hope <[email-masked]>
Date: Sat, 13 Apr 2013 11:16:53 +0200

Hi,

Regards, Gaute

On 12. april 2013 21:46, Hamish D wrote:
> 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 ...
> 
> We have emailed William about this but have had no response. So currently
> we have no access to publishing gems under the sup name.
>

---

From: Gaute Hope <[email-masked]>
Date: Mon, 15 Apr 2013 00:32:43 +0200

> Maybe we should move this list to the wiki.

Definitely: A roadmap for the next sup.

Cheers,
Gaute

---

From: Gaute Hope <[email-masked]>
Date: Sun, 14 Apr 2013 00:17:32 +0200

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

---

From: Gaute Hope <[email-masked]>
Date: Sat, 13 Apr 2013 19:14:04 +0200

On 13. april 2013 18:35, Jonathan Lassoff wrote:
> On Sat, Apr 13, 2013 at 6:17 AM, Gaute Hope <[email-masked]> wrote:
>> On la. 13. april 2013 kl. 12.09 +0200, Jonathan Lassoff wrote:
>>> On Sat, Apr 13, 2013 at 2:16 AM, Gaute Hope <[email-masked]> wrote:
>>>> Hi,
>>>>
>>> No, thank you very much! That looks great!
>>>
>>> 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

---

From: Eric Weikl <[email-masked]>
Date: Sun, 14 Apr 2013 13:31:14 +0200

Hi Gaute,

That sounds like a plan of action :-)

> - 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

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

+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

---

From: Gaute Hope <[email-masked]>
Date: Sun, 14 Apr 2013 14:05:52 +0200

> together with IMAP syncback, since both require a migration step by the

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).

> fairly easy to cherry-pick the relevant commits into the development

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.

> website, Redwood protocol stuff, etc.).

Yes, you could put Iconv in this category as well.

> recognizes that it wasn't done yet and asks you to run a command-line

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

> 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

---

From: Eric Weikl <[email-masked]>
Date: Tue, 16 Apr 2013 22:30:26 +0200

Hi everyone,

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:
>

---

From: Hamish D <[email-masked]>
Date: Fri, 12 Apr 2013 20:46:54 +0100

Hamish

---

From: Steven Schmeiser <[email-masked]>
Date: Thu, 15 Aug 2013 09:35:17 -0400

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:
> > 
> > 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:
> >

---

From: Jonathan Lassoff <[email-masked]>
Date: Fri, 12 Apr 2013 11:09:33 -0700

The crash was like:

Sincerely,
William

---

From: Eric Weikl <[email-masked]>
Date: Sun, 14 Apr 2013 19:39:53 +0200

Hi Gaute,

> - Manipulating IMAP could mess up user mail (potentially new bugs could

Yes. Although my experience was positive until now, this definitely needs
extensive testing (especially when disabled). Volunteers, anyone? :-)

> interested I could add you as commiter or owner.

Sure, I can give it a spin.

Cheers,
Eric

---

From: Jonathan Lassoff <[email-masked]>
Date: Sat, 13 Apr 2013 12:19:17 -0700

On Sat, Apr 13, 2013 at 10:37 AM, Gaute Hope <[email-masked]> 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

And target ncursesw?

> 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:
>>
>>

---

From: Gaute Hope <[email-masked]>
Date: Sat, 13 Apr 2013 15:29:08 +0200

> no one has the rights on this one ? I don't see anything in github for

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.

---

From: Gaute Hope <[email-masked]>
Date: Mon, 15 Apr 2013 13:42:28 +0200

> 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

---

From: Gaute Hope <[email-masked]>
Date: Wed, 17 Apr 2013 10:51:29 +0200

> [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

---

From: Jonathan Lassoff <[email-masked]>
Date: Sat, 13 Apr 2013 13:48:55 -0700

---

From: Gaute Hope <[email-masked]>
Date: Sat, 13 Apr 2013 15:17:37 +0200

Regards, Gaute

---

From: Steven Hum <[email-masked]>
Date: Tue, 16 Apr 2013 23:31:33 -0400

Beautiful! I will begin using this in place of my copy of ezyang's fork 
immediately.

Thanks for all your hard work,
Steven

-- 
"Truth or die."

Steven Hum  
5 - 28 Gilmour St  
Ottawa, ON K2P 0N3  
email [email-masked]  
tel 613.237.9058

---

From: Jonathan Lassoff <[email-masked]>
Date: Sat, 13 Apr 2013 09:35:53 -0700

Cheers,
jof

---

From: Eric Weikl <[email-masked]>
Date: Thu, 15 Aug 2013 15:22:14 +0200

Hi fellow sup users,

Cheers,
Eric

_______________________________________________
Sup-devel mailing list
[email-masked]
http://rubyforge.org/mailman/listinfo/sup-devel

---

From: Jonathan Lassoff <[email-masked]>
Date: Sat, 13 Apr 2013 03:09:55 -0700

--j

---

From: Gaute Hope <[email-masked]>
Date: Sat, 13 Apr 2013 19:37:01 +0200

For sup2:
- Fork a new repo: sup2

Would be very nice:
- Index migration
- Config migration

Regards, Gaute

---

From: Jonathan Lassoff <[email-masked]>
Date: Sat, 13 Apr 2013 12:15:10 -0700

http://supmua.org/

---

From: Steven Hum <[email-masked]>
Date: Sat, 13 Apr 2013 11:42:45 -0400

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

-- 
"Truth or die."

Steven Hum  
5 - 28 Gilmour St  
Ottawa, ON K2P 0N3  
email [email-masked]  
tel 613.237.9058