Greetings.
On Tue, 23 Apr 2013 15:23:59 +0200 "Roberto E. Vargas Caballero"
<k...@shike2.com> wrote:
> On Tue, Apr 23, 2013 at 10:50:32AM +0200, Christoph Lohmann wrote:
> The unique problem is utf8 encoding will put the 8 bit to 1 in some
> characters, so it is not very clear for me like applications can difference
> between meta-character and first byte of a utf8 sequence. I can see that
> terminfo has the following fields:
>
> km: Has a meta key
> rmm: turn off meta mode
> smm: turn on meta mode
>
> And the information about them is:
>
> If the terminal has a ``meta key'' which acts as a shift key, setting
> the 8th bit of any character transmitted, this fact can be indicated
> with km. Otherwise, software will assume that the 8th bit is parity
> and it will usually be cleared. If strings exist to turn this ``meta
> mode'' on and off, they can be given as smm and rmm.
>
>
> xterm has km capability but doesn't have rmm or smm. I suppouse that
The terminfo of my system has
smm=\E[?1034h
rmm=\E[?1034l
I’ve implemented it that way in st plus (as discussed on IRC) do the re‐
set capabilities now unset 8bit mode.
For the Op: Please try now, if your applications behave as expected when using
tput smm
beforehand.
Sincerely,
Christoph Lohmann
