8000 Conpty compatibility ? PTY+ utf-8 on windows10 fall 2018 · Issue #723 · prompt-toolkit/python-prompt-toolkit · GitHub
[go: up one dir, main page]
Skip to content

Conpty compatibility ? PTY+ utf-8 on windows10 fall 2018 #723

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
stonebig opened this issue Sep 8, 2018 · 1 comment
Closed

Conpty compatibility ? PTY+ utf-8 on windows10 fall 2018 #723

stonebig opened this issue Sep 8, 2018 · 1 comment

Comments

@stonebig
Copy link
Contributor
stonebig commented Sep 8, 2018

https://blogs.msdn.microsoft.com/commandline/2018/08/02/windows-command-line-introducing-the-windows-pseudo-console-conpty/

I guess it's good news for Python-prompt.
@jonathanslenders
Copy link
Member

Hi @stonebig,

Yes, this is absolutely great news. I've been following this blog for some time.

For prompt_toolkit, I think this doesn't offer anything new. However, in prompt_toolkit 2.0, we already take advantage of Windows 10 supporting ANSI escapes sequences for the output, and we use that when possible. This means we have 24 bit color support and better rendering speeds.

Conpty however is what I think will help me improve ptterm on Windows (https://github.com/jonathanslenders/ptterm) Right now, we use winpty which isn't that great, and the Python library, yawinpty that I use there, seems to be removed from GitHub. Windows PTY support will simplify things a lot.

@stonebig stonebig mentioned this issue Oct 22, 2018
Closed
@Stanzilla Stanzilla mentioned this issue May 4, 2020
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jonathanslenders @stonebig
0