From: Eli Zaretskii <eliz@gnu.org>
To: Akib Azmain Turja <akib@disroot.org>
Cc: rudi@constantly.at, emacs-devel@gnu.org
Subject: Re: Terminal emulator in Windows
Date: Wed, 11 Jan 2023 21:55:18 +0200 [thread overview]
Message-ID: <83358gn8wp.fsf@gnu.org> (raw)
In-Reply-To: <87r0w1kju7.fsf@disroot.org> (message from Akib Azmain Turja on Thu, 12 Jan 2023 00:27:28 +0600)
> From: Akib Azmain Turja <akib@disroot.org>
> Cc: rudi@constantly.at, emacs-devel@gnu.org
> Date: Thu, 12 Jan 2023 00:27:28 +0600
>
> >> > https://devblogs.microsoft.com/commandline/windows-command-line-introducing-the-windows-pseudo-console-conpty/
> >> >
> >>
> >> Hmm, a quick internet search reveals that the thing is an API, not an
> >> escape sequence protocol like the VT series terminals or ECMA-48
> >> specification.
> >
> > It is actually both. The pseudo-console supports SGR sequences. But
> > it has other problems...
> >
>
> What?
Mainly its assumptions about the encoding of text read and written
through it. I explained that here several times in the past, and I
filed an issue with the conpty developers.
next prev parent reply other threads:[~2023-01-11 19:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 8:08 Terminal emulator in Windows Akib Azmain Turja
2023-01-10 13:25 ` Eli Zaretskii
2023-01-10 16:15 ` Akib Azmain Turja
2023-01-10 17:06 ` Eli Zaretskii
2023-01-11 9:35 ` Akib Azmain Turja
2023-01-11 10:14 ` Po Lu
2023-01-11 12:48 ` Eli Zaretskii
2023-01-11 13:01 ` Po Lu
2023-01-11 13:19 ` Eli Zaretskii
2023-01-11 14:19 ` Rudolf Schlatte
2023-01-11 15:18 ` Akib Azmain Turja
2023-01-11 17:01 ` Eli Zaretskii
2023-01-11 18:27 ` Akib Azmain Turja
2023-01-11 19:55 ` Eli Zaretskii [this message]
2023-01-11 15:26 ` Akib Azmain Turja
2023-01-11 12:42 ` Eli Zaretskii
2023-01-11 15:11 ` Akib Azmain Turja
2023-01-11 17:01 ` Eli Zaretskii
2023-01-11 17:31 ` Jim Porter
2023-01-11 18:26 ` Akib Azmain Turja
2023-01-11 19:52 ` Jim Porter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83358gn8wp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=akib@disroot.org \
--cc=emacs-devel@gnu.org \
--cc=rudi@constantly.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.