on tue, sep 01, 2015 at 08:52:26am +0300, otto modinos wrote:
It's not a locking escape. "ESC ( 0" switches your character
set to VT100 Special Graphics (see [0]).
Of course, if a given terminal like mosh doesn't have the
translation-tables, nothing gets "messed" up.
mosh mentions some "UTF8
> >mosh mentions some "UTF8 terminal mode", which is different
> >from "ISO 2022" and doesn't even have G0-3. It's all mentioned
> >in the link[1].
> >
> >[1]: https://www.cl.cam.ac.uk/~mgk25/unicode.html#term
This is the personal opinion of the author of the article. Can
you send me a link to
On Tue, Sep 01, 2015 at 08:30:59AM +0200, Roberto E. Vargas Caballero wrote:
>mosh mentions some "UTF8 terminal mode", which is different
>from "ISO 2022" and doesn't even have G0-3. It's all mentioned
>in the link[1].
>
>[1]: https://www.cl.cam.ac.uk/~mgk25/unicode.html#term
This is the
> This is the personal opinion of the author of the article. Can
> you send me a link to the standard where it is said?. The problem
> with terminals is they stop their evolution at the beginning
> of the 90, so there is no standard way of doing utf8 stuff.
I know, I was just trying to explain
On Tue, Sep 01, 2015 at 10:22:52PM +0800, Pickfire wrote:
> Hi, it seems that st does some terminal codes abnormally[1].
>
> What is the reason for st's key codes to be different from the other
> terminals? Is st following some standards?
>
> [1]:
>
