[GH-ISSUE #566] Replaying recording shows (newlines at every new character in kitty/alacritty) with a specific shell setup #306

Closed
opened 2026-02-25 20:33:17 +03:00 by kerem · 5 comments
Owner

Originally created by @AkechiShiro on GitHub (Aug 21, 2023).
Original GitHub issue: https://github.com/asciinema/asciinema/issues/566

Describe the bug
Replay looks like this :
image

To Reproduce
Steps to reproduce the behavior:
0. Open Kitty terminal

  1. asciinema rec -i 2 rec.rec
  2. Write commands
  3. If bash is used as a shell (in Kitty via the terminal, then the issue is gone/fixed temporarily)
  4. See error

Expected behavior
Replay should be replayed correctly in Kitty using Zsh and Powerlevel11k shell theme with a NerdFont patched.

Versions:

  • OS: ArchLinux
  • asciinema cli: asciinema 2.3.0

Additional contextAdd any other context about the problem here.

See 3.

Originally created by @AkechiShiro on GitHub (Aug 21, 2023). Original GitHub issue: https://github.com/asciinema/asciinema/issues/566 **Describe the bug** Replay looks like this : ![image](https://github.com/asciinema/asciinema/assets/14914796/d5461930-5233-4e17-ba91-7a7596714744) **To Reproduce** Steps to reproduce the behavior: 0. Open Kitty terminal 1. asciinema rec -i 2 rec.rec 2. Write commands 3. If bash is used as a shell (in Kitty via the terminal, then the issue is gone/fixed temporarily) 4. See error **Expected behavior** Replay should be replayed correctly in Kitty using Zsh and Powerlevel11k shell theme with a NerdFont patched. **Versions:** - OS: ArchLinux - asciinema cli: asciinema 2.3.0 **Additional context**Add any other context about the problem here. See 3.
kerem closed this issue 2026-02-25 20:33:17 +03:00
Author
Owner

@AkechiShiro commented on GitHub (Aug 21, 2023):

Do you need the capture or will you be able to reproduce the issue ?

<!-- gh-comment-id:1686440599 --> @AkechiShiro commented on GitHub (Aug 21, 2023): Do you need the capture or will you be able to reproduce the issue ?
Author
Owner

@AkechiShiro commented on GitHub (Aug 21, 2023):

I believe #368 is the fix, why is it not yet merged in ?

<!-- gh-comment-id:1686442196 --> @AkechiShiro commented on GitHub (Aug 21, 2023): I believe #368 is the fix, why is it not yet merged in ?
Author
Owner

@AkechiShiro commented on GitHub (Aug 21, 2023):

@ku1ik

<!-- gh-comment-id:1686443015 --> @AkechiShiro commented on GitHub (Aug 21, 2023): @ku1ik
Author
Owner

@AkechiShiro commented on GitHub (Aug 21, 2023):

I haven't tested the fix yet, but will soon.

<!-- gh-comment-id:1686447608 --> @AkechiShiro commented on GitHub (Aug 21, 2023): I haven't tested the fix yet, but will soon.
Author
Owner

@ku1ik commented on GitHub (Nov 2, 2023):

#368 is not a fix that resolves the issue here, it just adds a warning. You would still get broken output if we merged it.

There's no easy fix for this, as you can't really fit longer lines (recorded) into shorter lines (current terminal width during playback).

The best we can do is to add the warning so user can expect corrupted output, but we can potentially detect if the corruption would happen (see https://github.com/asciinema/asciinema/pull/368#issuecomment-1790572425 for the idea).

<!-- gh-comment-id:1790586769 --> @ku1ik commented on GitHub (Nov 2, 2023): #368 is not a fix that resolves the issue here, it just adds a warning. You would still get broken output if we merged it. There's no easy fix for this, as you can't really fit longer lines (recorded) into shorter lines (current terminal width during playback). The best we can do is to add the warning so user can expect corrupted output, but we can potentially detect if the corruption would happen (see https://github.com/asciinema/asciinema/pull/368#issuecomment-1790572425 for the idea).
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/asciinema#306
No description provided.