You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Debugging terminal emulators in notoriously hard. It boils down to carefully analyzing the escape sequences produced by the app under investigation and ensuring Screen state is consistent with what is expected.
Right now pyte has two debugging tools:
pyte.DebugStream which emits JSON messages for each dispatched event; and
examples/webterm.py
I think some kind of a reverse-time debugger could be a very useful addition to that. It could augment the web UI we currently have with a time slider, which, when dragged, would play back (or forward) the recorded events.
The text was updated successfully, but these errors were encountered:
Debugging terminal emulators in notoriously hard. It boils down to carefully analyzing the escape sequences produced by the app under investigation and ensuring
Screen
state is consistent with what is expected.Right now
pyte
has two debugging tools:pyte.DebugStream
which emits JSON messages for each dispatched event; andexamples/webterm.py
I think some kind of a reverse-time debugger could be a very useful addition to that. It could augment the web UI we currently have with a time slider, which, when dragged, would play back (or forward) the recorded events.
The text was updated successfully, but these errors were encountered: