I contacted the maintainer of editline (libedit) and with his help, was able to create a patch so that it handles UTF-8 characters. I have also forwarded the patch to the developer.
Sent from my iPhone > On Oct 26, 2014, at 6:07 PM, Ryan Schmidt <[email protected]> wrote: > > >>> On Oct 26, 2014, at 10:22 AM, Mark Brethen wrote: >>> >>>> On Oct 26, 2014, at 4:12 AM, Ryan Schmidt wrote: >>>> >>>> On Oct 24, 2014, at 6:56 PM, Mark Brethen wrote: >>>> >>>> I've found that compiling against macports libedit, which is configured >>>> for wide-char/UTF-8 (--enable-widec option), breaks tab completion. The >>>> program that I'm building is bundled with libedit and compiles it without >>>> UTF-8 support. In this case tab completion works. Is it okay to install >>>> this linked libedit library as part of the port? >>> >>> Sure, whatever works best for that program. >>> >>> The obvious concern would be: does that impeded the program's ability to >>> process UTF-8 input? >> >> I think it uses the standard ASCII character set, but I'll check. > > Well libedit and libreadline are used in the process of acquiring user input. > Can you guarantee that the user will only input ASCII characters? What > happens if the user inputs other characters? > _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
