Sebastien Marie wrote:
> While testing ksh, I found the following problem, that I will try to
> describe. But I dunno if it is just a case no-managed by your patch. It
> looks like a problem in "inserting a UTF-8 char inside the line (opposed
> to 'at end of line')".
This is what Ingo meant by
Hi Sebastien,
Sebastien Marie wrote on Tue, Dec 08, 2015 at 07:06:57AM +0100:
> On Tue, Dec 08, 2015 at 01:19:35AM +0100, Ingo Schwarze wrote:
>> i'd like to propose a simplified version of this patch Frederic Nowak
>> posted a few weeks ago for commit. Our experience is probably
>> not yet
On Tue, Dec 08, 2015 at 01:19:35AM +0100, Ingo Schwarze wrote:
> Hi,
>
> i'd like to propose a simplified version of this patch Frederic Nowak
> posted a few weeks ago for commit. Our experience is probably
> not yet sufficient to develop a full-blown solution for all UTF-8
> problems in ksh(1),
Hi there,
I got annoyed with ksh(1) for messing up my command line after
accidentally entering an umlaut and decided to take a stab at teaching
it some utf8. The diff is inspired by Ted Unangst's recent patches for
e.g. rs[0].
It works for my use cases and seems to handle 2-byte (ßüöä) and
