-
Notifications
You must be signed in to change notification settings - Fork 6
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
Able to merge in UTF-8 supporting fork of Linenoise into our version? #20
Comments
UTF-8 support would be fantastic! I worked on this a little bit last year, but I don't remember which stumbling blocks I encountered that prevented me from finalizing the work. I'm on vacation right now, but I'll have a look after I get back. |
Another fork worth looking at: https://github.com/arangodb/linenoise-ng |
(Note to self: look at journal entries for late March/early April 2016) |
Another fork to consider incorporating (not UTF-8 related, but still): antirez/linenoise#113 |
linenoise-ng supposedly has Windows support. That would be really awesome :) Then we can support UTF-8 and all operating systems! |
Provides Windows and UTF-8 support There's some GCC-specific flags in Makefile.in, so this isn't suitable for Windows installation yet See GH #20
@samcv I added support in the |
Are the requirements from LibraryMake available now? If not, how can I point my project to use the multi-byte version of this? I've tried to clone the repository and build it myself, but there are no "build from source" instructions and I was unable to figure it out on my own. Thanks! |
@mcreenan I just took a quick look at the LibraryMake source - from what I can tell, sadly, that information is still not available =( If you're using GCC, cloning the repository and doing a |
Ah. I'll look into porting, but I haven't done C or C++ in 10+ years. |
See here:
https://github.com/yhirose/linenoise/tree/utf8-support
Would be great if we had UTF-8 support for this, as it's really an issue especially for a programming language that can use Unicode characters.
The text was updated successfully, but these errors were encountered: