You can check if libedit is linked ncursesw. That said, unicode support is not magic, ncursesw provide alternate api for unicode, callers must specifically call to unicode api to get job done, I don't know libedit have done that or not, you can check its source code.
On Fri, Jul 12, 2019, 2:12 AM Štěpán Němec <[email protected]> wrote: > On Thu, 11 Jul 2019 13:50:08 -0400 > Raul Miller wrote: > > > On Thu, Jul 11, 2019 at 1:31 PM Štěpán Němec <[email protected]> wrote: > >> Oh, I see. OTOH upstream claims to have supported unicode since 2016 > >> (cf. <https://thrysoee.dk/editline/>). That said, I have encountered > >> problems with (current) libedit unicode support with other programs as > >> well, so apparently there are still problems. > > > But libedit isn't distributed with j, and many OS vendors distribute a > > version compiled in 2014 (for example). > > That's why I put the "(current)" above. I'm using the latest libedit > version (20190324-3.1), built with plain configure && make without any > patches. Go figure... > > -- > Štěpán > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
