MIME-Version: 1.0
In-Reply-To: <20170401094231.cimb5lz43eo34jfp@angband.pl>
References: <20170401094231.cimb5lz43eo34jfp@angband.pl>
From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Sat, 1 Apr 2017 11:09:40 -0700
Message-ID: <CAADWXX_gG8JyFYoC_Dfer3QQCMo0_jwwYGcN22b7M-ueGqjW7A@mail.gmail.com>
Subject: Re: [GIT PULL] runes
To: Adam Borowski <kilobyte@angband.pl>
Cc: lkml <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset=UTF-8
Sender: linux-kernel-owner@vger.kernel.org
Content-Transfer-Encoding: 8bit
Content-Length: 1211
Lines: 28

On Sat, Apr 1, 2017 at 2:42 AM, Adam Borowski <kilobyte@angband.pl> wrote:
>
> It contains fixes for OLCUC handling, expanding its functionality to what I
> presume was your intention in implementing OLCUC in 1991 but couldn't be
> done then.

Yes, sadly, back then I was basically limited to Latin1, which is
obviously useless.

> With the fixes, to get the old-style OLCUC behaviour ASCII you can stty
> -iutf8; neither ANSI codes nor Unicode will be mangled anymore.  But, that's
> quite useless -- I wonder what was your reason to implement OLCUC back in
> the day even though it was obsolete by decades even then, and was already
> dropped from relevant standards.  Thus, I guess you want proper rune
> support, this pull request adds this.  I've chosen Elder Futhark as the
> variant to implement.

The question that obviously springs to mind is why you didn't make
this the default state of a tty? As it is, it seems that people have
to do extra work (and know about this feature) to get the Great Runes
enabled.

That seems user-hostile and counter-productive?

Also, sadly, gmail seems hostile to this whole thing, and marked your
email as spam. Don't ask me why.

                     ᛚᛁᚾᚢᛊ