Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge with official ruby/curses? #22

Open
gauteh opened this issue Jan 29, 2014 · 4 comments
Open

Merge with official ruby/curses? #22

gauteh opened this issue Jan 29, 2014 · 4 comments

Comments

@gauteh
Copy link
Member

gauteh commented Jan 29, 2014

https://github.com/ruby/curses

Complement issue: ruby/curses#2

@avtobiff
Copy link

Yes! Beware of licensing though.

@gauteh
Copy link
Member Author

gauteh commented Mar 20, 2014

At this point I can't see anything in curses that is not already implemented in ncursesw. So I guess merging is more about abandoning the curses gem, potentially implement missing stuff. Maybe it will run its own course.

Deprecation: https://github.com/ruby/ruby/blob/ruby_2_1/NEWS#L344

@lorenrogers
Copy link

Has there been any movement on this in the past couple years?

@gauteh
Copy link
Member Author

gauteh commented Nov 4, 2016

Loren Rogers writes on november 4, 2016 1:12:

Has there been any movement on this in the past couple years?

Nope - I don't know what is happening with the official bindings. They
were incomplete last time I checked. As mentioned before, merging is
more a matter of closing one of the projects - untill the official one
is feature-complete it is no point in closing this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants