Skip to content

feature: handle asciicast v2 input and marker event codes #576

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
Open
azerella opened this issue May 5, 2025 · 1 comment
Open

feature: handle asciicast v2 input and marker event codes #576

azerella opened this issue May 5, 2025 · 1 comment

Comments

@azerella
Copy link

azerella commented May 5, 2025 •
edited
Loading

sshpiper does not handle recording input or markers event types as per the asciicast > v2 event spec. All commands are logged as o / output instead of recording user input?

Is this a bug or a feature or the SSH session?

See the asciicast v2 event code spec:

https://docs.asciinema.org/manual/asciicast/v2/#supported-event-codes
@azerella azerella changed the title bug: asciicast v2 event code handling feature: handle asciicast v2 input and marker event codes May 5, 2025
@tg123
Copy link
Owner

tg123 commented May 7, 2025

sshpiper record the result from upstream only, so everything was treated as output

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
@tg123 @azerella