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

[discussion] Why both libtermkey and libncurses? #428

Closed
ghost opened this issue Dec 13, 2016 · 3 comments
Closed

[discussion] Why both libtermkey and libncurses? #428

ghost opened this issue Dec 13, 2016 · 3 comments

Comments

@ghost
Copy link

ghost commented Dec 13, 2016

I am only asking because I am curious.

Unlike libncurses, libtermkey is rarely pre-installed on a system, and everything could have been done with libncurses.

Is that the reason ? With libtermkey the way to go as libncurses can not evolve anymore ?

If one had to start a whole new project, would you recommand libtickit ? There was a depcrecation notice on the libtermkey page pointing at libtickit as a replacement.

@aeosynth
Copy link
Contributor

libtermkey is deprecated, but libtickit is not ready to replace it + curses:

neovim/neovim#5556 (comment)

Ultimately this entire behaviour would become a lot simpler in neovim if it just used libtickit to handle terminal IO; though I'm aware it's not quite ready for that yet.

@erf
Copy link
Contributor

erf commented Dec 15, 2016

@josuah see #250

@ghost
Copy link
Author

ghost commented Dec 15, 2016

Thanks you for pointing me out these issues. Got plenty to read now. :)

@ghost ghost closed this as completed Dec 15, 2016
This issue was closed.
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

2 participants