-
Notifications
You must be signed in to change notification settings - Fork 28
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.
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
Garbled output on Telnet Client #269
Comments
Hi @Robatronic, thanks for reaching out! I have two questions regarding your use-case of pywinpty:
|
|
Here's what I wrote:
|
This is the output on connecting:
|
...then, after hitting enter and typing in dir....
|
Telnet settings: Escape Character is 'CTRL+]' |
Looking at it, I'm starting to wonder if some of the escape codes aren't being sent as an atomic unit..... |
The terminado project is very slick. I'm trying to do similar with regular sockets rather than websockets..... |
Does terminado outputs the program correctly? |
It does I first found Terminado in Jupyterlab and dug in to find it uses pyWinPty. I have another experiment I want to do to try and track down where the issue is. |
I'm trying to write a wrapper around Windows console apps that will allow me to connect to their stdio from network/remote clients. It is a VERY pared down concept of what Terminado does.
Each new connection gets a "reader" task that writes directly to the subprocess stdin and there is a "writer" class that monitors a global queue of pty output and forwards the bytes on to all connected clients. The connected clients are a list of writers in a global variable as is the PTY_PROC object.
There is also the pty_reader, that takes text from the PTY and puts it on the global byte queue.
I am testing using Telnet. I get some good data to the client, but some of it is garbled up. Mainly:
So far, I've tried matching columns (80) and rows (24) and have been looking in to different terminal settings (i.e VT100, etc), but to no avail.
I'm hoping it's something simple and "obvious".
The core essentials (I believe) are here:
The text was updated successfully, but these errors were encountered: