[GH-ISSUE #39] Cannot confirm/deny upload after finished recording (OSX) #629

Closed
opened 2026-03-15 04:28:23 +03:00 by kerem · 5 comments
Owner

Originally created by @jerluc on GitHub (Oct 2, 2013).
Original GitHub issue: https://github.com/asciinema/asciinema/issues/39

After recording in the terminal, I press Ctrl+d, which prints out (the extra indentation on the second line is literally how it shows up):

~ Asciicast recording finished.
                               ~ Do you want to upload it? [Y/n]

After this point, I cannot confirm nor deny the upload. In fact, if I type anything it does not show up in the terminal after the above is displayed.

Originally created by @jerluc on GitHub (Oct 2, 2013). Original GitHub issue: https://github.com/asciinema/asciinema/issues/39 After recording in the terminal, I press Ctrl+d, which prints out (the extra indentation on the second line is literally how it shows up): ``` ~ Asciicast recording finished. ~ Do you want to upload it? [Y/n] ``` After this point, I cannot confirm nor deny the upload. In fact, if I type anything it does not show up in the terminal after the above is displayed.
kerem closed this issue 2026-03-15 04:28:37 +03:00
Author
Owner

@ku1ik commented on GitHub (Oct 2, 2013):

@jerluc thanks for reporting. I know what's happening. The fix is in the works. I'll let you know about the new release.

<!-- gh-comment-id:25581866 --> @ku1ik commented on GitHub (Oct 2, 2013): @jerluc thanks for reporting. I know what's happening. The fix is in the works. I'll let you know about the new release.
Author
Owner

@ku1ik commented on GitHub (Oct 2, 2013):

@jerluc thanks for reporting. I know what's happening. The fix is in the works. I'll let you know about the new release.

<!-- gh-comment-id:25581866 --> @ku1ik commented on GitHub (Oct 2, 2013): @jerluc thanks for reporting. I know what's happening. The fix is in the works. I'll let you know about the new release.
Author
Owner

@ku1ik commented on GitHub (Oct 3, 2013):

@jerluc It's fixed now, please update.

<!-- gh-comment-id:25604881 --> @ku1ik commented on GitHub (Oct 3, 2013): @jerluc It's fixed now, please update.
Author
Owner

@jerluc commented on GitHub (Oct 4, 2013):

Awesome, works perfect now! Can attach a commit to this issue? Would love to see the underlying cause.

<!-- gh-comment-id:25720741 --> @jerluc commented on GitHub (Oct 4, 2013): Awesome, works perfect now! Can attach a commit to this issue? Would love to see the underlying cause.
Author
Owner

@ku1ik commented on GitHub (Oct 4, 2013):

This is the fix b02e826. I had it in the past but forgot to enable it after last refactoring. I still don't know why this happens (and it happens only on OSX). I need to investigate it deeper.

<!-- gh-comment-id:25730461 --> @ku1ik commented on GitHub (Oct 4, 2013): This is the fix b02e826. I had it in the past but forgot to enable it after last refactoring. I still don't know why this happens (and it happens only on OSX). I need to investigate it deeper.
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#629
No description provided.