linux-kernel - Re: [ANNOUNCE] Kconfiglib menuconfig implementation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAFkk2KTPiNCWNLncz2KZB66W68YS2H348=bQsgsdqKT1fLRjMw@mail.gmail.com>
Date:   Fri, 4 May 2018 00:48:14 +0200
From:   Ulf Magnusson <ulfalizer@...il.com>
To:     Randy Dunlap <rdunlap@...radead.org>
Cc:     Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [ANNOUNCE] Kconfiglib menuconfig implementation

On Thu, May 3, 2018 at 10:28 PM, Randy Dunlap <rdunlap@...radead.org> wrote:
> Hi,
>
> (with new kconfiglib.py and menuconfig.py)
>
> Thanks for the fixes.
>
> If I use "LC_CTYPE=C.UTF-8" then I get the down arrows in the bottom colored
> bar.  Without that, I get an upside-down T (that is 193, 0xc1, line drawing
> character in the IBM extended character set).
>
> Hm. With LC_CTYPE=C.UTF-8, the upper colored bar prints up arrows.
> Without that, it prints ^^^^^^^^^^^^^^.
> That's nice that it can do either.

The arrows use ACS_U/DARROW from the alternate character set. You get
nice Unicode arrows for those with ncurses/PDCurses, plus "fallbacks"
(strictly speaking the Unicode arrows are fallbacks too).

Unicode text entry is still broken with LC_CTYPE=C, because ncurses
respects it. Having the menuconfig just force C.UTF-8 if it's
available might fix a bunch of problems in practice, even if it feels
a bit iffy to force settings.

Python 3.7 will improve things at least. It converts LC_CTYPE=C into
LC_CTYPE=<some available UTF-8 locale>.

Cleanest would be if all environments sanely defaulted to UTF-8, but
that's not how it is in practice, unfortunately. :)

>
> Being a vim user, I do like the optional navigation keys.
>
> --
> ~Randy

Cheers,
Ulf