Hi, I found something that st display wrongly. I got it from
https://mosh.mit.edu/#techinfo
For ISO 2022 locking escapes:
me@alarmpi ~> echo -e "\033(0"
me@alarmpi ~>
St does this:
me@alarmpi ~> echo -e "\033(0"
␋┴▒┼@▒┌▒⎼└⎻␋ ·>
For Evil escape sequences:
me@alar
On Sun, Aug 30, 2015 at 04:10:28PM +0200, Christoph Lohmann wrote:
Greetings.
The st parsing of the escape sequences is easy to grasp in five minutes.
Please send in a patch when you fixed it.
Sincerely,
Christoph Lohmann
"Be resolute, fear no sacrifice and surmount every difficulty to win v
On Sun, 30 Aug 2015 21:19:09 +0800
Pickfire wrote:
Hey Pickfire,
> For ISO 2022 locking escapes:
>
> me@alarmpi ~> echo -e "\033(0"
>
> me@alarmpi ~>
>
> St does this:
>
> me@alarmpi ~> echo -e "\033(0"
>
> ␋┴▒┼@▒┌▒⎼└⎻␋ ·>
It's not a locking escape. "ESC ( 0" s
On Mon, Aug 31, 2015 at 11:30:54AM +0200, FRIGN wrote:
For Evil escape sequences:
me@alarmpi ~> echo -e "xyz\033[2;2H\0314\0202\nhello"
xŷz
hello
me@alarmpi ~>
St does this:
me@alarmpi ~> echo -e "xyz\033[2;2H\0314\0202\nhello"
x̂z
hello
me@alarmpi ~>
This goe
On Mon, 2015-08-31 at 15:13 +0200, Christoph Lohmann wrote:
> Greetings.
>
> On Mon, 31 Aug 2015 15:13:14 +0200 FRIGN wrote:
> > On Sun, 30 Aug 2015 21:19:09 +0800
> > Pickfire wrote:
> > > For Evil escape sequences:
> > >
> > > me@alarmpi ~> echo -e "xyz\033[2;2H\0314\0202\nhello"
> > >
On Mon, 31 Aug 2015 17:05:39 +0200
Joakim Sindholt wrote:
> With the WIP combining character patch I sent to the list some time ago
> now it shows as "x̂yz" (but does other weird things when entered into a
> non-empty terminal). gnome-terminal behaves equally weird with moving
> the cursor some a
> > For ISO 2022 locking escapes:
> >
> > me@alarmpi ~> echo -e "\033(0"
> >
> > me@alarmpi ~>
> >
> > St does this:
> >
> > me@alarmpi ~> echo -e "\033(0"
> >
> > ␋┴▒┼@▒┌▒⎼└⎻␋ ·>
>
> It's not a locking escape. "ESC ( 0" switches your character
> set to VT100 Special Graphics (see [
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 t
> >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 th
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 person
> 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 wh
11 matches
Mail list logo
