-
Notifications
You must be signed in to change notification settings - Fork 52
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
Tlog-play receives input from recording #147
Comments
OK, no, what's likely is the recording asking the terminal for reports, and the playback terminal dutifully replying. |
It doesn't seem like we can stop the terminal from replying to the control sequences and we can't read the control keys from anywhere but the terminal. We should either filter out the request control sequences from the output or the response control sequences from the input, whichever is easier and more reliable. The most reliable way, however, might be embedding a terminal emulator as #91 describes. |
Attempt to filter out some common control sequences coming from the terminal in response to control sequences from recordings, on playback. This alleviates Scribery#147, but it would require embedding a terminal emulator to properly fix it.
Attempt to filter out some common control sequences coming from the terminal in response to control sequences from recordings, on playback. This alleviates Scribery#147, but it would require embedding a terminal emulator to properly fix it.
Attempt to filter out some common control sequences coming from the terminal in response to control sequences from recordings, on playback. This alleviates Scribery#147, but it would require embedding a terminal emulator to properly fix it.
Apparently some recorded sessions can include control characters prompting the playback terminal to emulate input, which can then be interpreted by tlog-play as playback controls pausing or quitting the playback and potentially doing anything. An example could be a vim editing session.
I wasn't able to quickly find out how that happens exactly and how to deal with that, but we need to find it out and fix this. Perhaps check other playback programs for solutions.
The text was updated successfully, but these errors were encountered: