On Wed, Feb 9, 2011 at 2:04 PM, Rodrigo Rosenfeld Rosas <rr.ro...@gmail.com> wrote: > I've talked about it to you on RubyConf Brazil 2010, but I'll point the > patches again in case you have missed it: > > http://sourceforge.net/tracker/?func=detail&aid=3090708&group_id=64033&atid=506056 > <http://sourceforge.net/tracker/?func=detail&aid=3090708&group_id=64033&atid=506056> > http://sourceforge.net/tracker/?func=detail&aid=3090685&group_id=64033&atid=506056 > <http://sourceforge.net/tracker/?func=detail&aid=3090685&group_id=64033&atid=506056> > > Please, ask me if you have any questions.
Ahh yes, I remember now :) We have stalled on the jline issue largely because it has been forked to death (dozens of incompatible forks) and we don't want to own it. Your patches may fix problems, and it's likely there are other jline forks that would also fix those problems, but we haven't been able to sort out whether there's even a canonical jline repository anymore. What might be more useful than trying to fix jline would be checking to see if alternatives like readline-ffi or rb-readline work correctly on all platforms: https://github.com/koichiro/readline-ffi https://github.com/luislavena/rb-readline I know it's frustrating to have jline still not working properly for some users, but I'm honestly not sure of the best way to proceed with jline fixes anymore :( - Charlie --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
