From: Randy Dunlap <rdunlap@infradead.org>
To: Ulf Magnusson <ulfalizer@gmail.com>
Cc: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] Kconfiglib menuconfig implementation
Date: Thu, 3 May 2018 17:05:46 -0700 [thread overview]
Message-ID: <2e646e4d-4d3d-a81e-83e3-59875b425ea8@infradead.org> (raw)
In-Reply-To: <CAFkk2KTPiNCWNLncz2KZB66W68YS2H348=bQsgsdqKT1fLRjMw@mail.gmail.com>
On 05/03/2018 03:48 PM, Ulf Magnusson wrote:
> On Thu, May 3, 2018 at 10:28 PM, Randy Dunlap <rdunlap@infradead.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).
Too bad it doesn't use "vvvvvvvvvvvvvv" for the down-arrow fallbacks.
Instead of that funky IBM PC line drawing stub.
> 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. :)
thanks,
--
~Randy
next prev parent reply other threads:[~2018-05-04 0:05 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-01 0:57 Ulf Magnusson
2018-05-01 17:56 ` Randy Dunlap
2018-05-01 18:13 ` Randy Dunlap
2018-05-01 18:52 ` Randy Dunlap
2018-05-01 19:33 ` Ulf Magnusson
2018-05-03 2:47 ` Ulf Magnusson
2018-05-03 20:31 ` Randy Dunlap
2018-05-03 21:26 ` Ulf Magnusson
2018-05-01 19:12 ` Ulf Magnusson
2018-05-01 19:47 ` Ulf Magnusson
2018-05-01 21:07 ` Ulf Magnusson
2018-05-03 20:28 ` Randy Dunlap
2018-05-03 22:48 ` Ulf Magnusson
2018-05-04 0:05 ` Randy Dunlap [this message]
2018-05-08 16:59 ` Ulf Magnusson
2018-05-11 1:22 ` Ulf Magnusson
2018-05-20 3:45 ` Randy Dunlap
2018-05-20 3:51 ` Randy Dunlap
2018-05-20 4:24 ` Ulf Magnusson
2018-05-20 5:50 ` Ulf Magnusson
2018-05-20 4:03 ` Randy Dunlap
2018-05-20 4:47 ` Ulf Magnusson
2018-05-20 5:13 ` Ulf Magnusson
2018-05-21 2:45 ` Randy Dunlap
2018-05-21 3:33 ` Ulf Magnusson
2018-05-21 3:47 ` Randy Dunlap
2018-05-22 10:18 ` Ulf Magnusson
2018-05-25 22:06 ` Randy Dunlap
2018-05-20 7:51 ` Ulf Magnusson
2018-05-21 2:22 ` Randy Dunlap
2018-05-20 6:03 ` Ulf Magnusson
2018-05-14 16:58 ` Pavel Machek
2018-05-14 18:12 ` Ulf Magnusson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2e646e4d-4d3d-a81e-83e3-59875b425ea8@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ulfalizer@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®