starred/asciinema

Fork 0

mirror of https://github.com/asciinema/asciinema.git synced 2026-04-25 16:05:52 +03:00

[GH-ISSUE #122] Support for `--silent` option #92

New issue

Closed

opened 2026-02-25 20:32:34 +03:00 by kerem · 11 comments

kerem commented

2026-02-25 20:32:34 +03:00

Owner

Originally created by @lenka21 on GitHub (Jul 21, 2015).
Original GitHub issue: https://github.com/asciinema/asciinema/issues/122

right now before recording started I always see:

~ Asciicast recording started.
~ Hit Ctrl-D or type "exit" to finish.

and similar

~ Asciicast recording finished.
~ Press <Enter> to upload, <Ctrl-C> to cancel.

at the end.

it would be great to have a possibility of suppressing this messages. I have found, that simple redirecting the output doesn't work, because then nothing is displayed.

With that option I would have a possobility to record everything what other guys write on our common server. Simply enry in default .zshrc will do the job:

exec asciinema rec $ASCIIHOME/`timestamp` -w 3 -y -s -c /bin/bash

Originally created by @lenka21 on GitHub (Jul 21, 2015). Original GitHub issue: https://github.com/asciinema/asciinema/issues/122 right now before recording started I always see: ``` ~ Asciicast recording started. ~ Hit Ctrl-D or type "exit" to finish. ``` and similar ``` ~ Asciicast recording finished. ~ Press <Enter> to upload, <Ctrl-C> to cancel. ``` at the end. it would be great to have a possibility of suppressing this messages. I have found, that simple redirecting the output doesn't work, because then nothing is displayed. With that option I would have a possobility to record everything what other guys write on our common server. Simply enry in default `.zshrc` will do the job: ``` exec asciinema rec $ASCIIHOME/`timestamp` -w 3 -y -s -c /bin/bash ```

kerem closed this issue

2026-02-25 20:32:34 +03:00

kerem commented

2026-02-25 20:32:35 +03:00

Author

Owner

@ku1ik commented on GitHub (Jul 21, 2015):

That's a great idea, and seems to be easy to implement. Thanks!

@ku1ik commented on GitHub (Jul 21, 2015): That's a great idea, and seems to be easy to implement. Thanks!

kerem commented

2026-02-25 20:32:35 +03:00

Author

Owner

@noisy commented on GitHub (Aug 7, 2015):

@sickill: any ETA?

@noisy commented on GitHub (Aug 7, 2015): @sickill: any ETA?

kerem commented

2026-02-25 20:32:35 +03:00

Author

Owner

@ku1ik commented on GitHub (Aug 7, 2015):

Um, no ETA, sorry. But I'm happy to accept PR :)

@ku1ik commented on GitHub (Aug 7, 2015): Um, no ETA, sorry. But I'm happy to accept PR :)

kerem commented

2026-02-25 20:32:35 +03:00

Author

Owner

@noisy commented on GitHub (Aug 7, 2015):

@sickill I do not know go yet :( And today, when I tried to just remove code responsible for printing this message, I had a problem to properly compile a binary. Regardless of my changes, I always endup with version which produce this message. I am not sure how go building process works, but I am afraid, that somehow during build I unintentionally fetched original sources from last release tag.

@noisy commented on GitHub (Aug 7, 2015): @sickill I do not know go yet :( And today, when I tried to just remove code responsible for printing this message, I had a problem to properly compile a binary. Regardless of [my changes](https://github.com/noisy/asciinema/commit/3af95d2e8d89564c2e06e9f661c68d49a6efaaa4), I always endup with version which produce this message. I am not sure how go building process works, but I am afraid, that somehow during build I unintentionally fetched original sources from last release tag.

kerem commented

2026-02-25 20:32:35 +03:00

Author

Owner

@ku1ik commented on GitHub (Aug 8, 2015):

It's in master. Can you pull and test it on your side?

@ku1ik commented on GitHub (Aug 8, 2015): It's in master. Can you pull and test it on your side?

kerem commented

2026-02-25 20:32:35 +03:00

Author

Owner

@noisy commented on GitHub (Aug 9, 2015):

@sickill it works as expected! Thanks! :)

@noisy commented on GitHub (Aug 9, 2015): @sickill it works as expected! Thanks! :)

kerem commented

2026-02-25 20:32:35 +03:00

Author

Owner

@aksh7860 commented on GitHub (Jul 31, 2019):

Hi,
@sickill is this feature available in asciinema version 2.0.2

@aksh7860 commented on GitHub (Jul 31, 2019): Hi, @sickill is this feature available in asciinema version 2.0.2

kerem commented

2026-02-25 20:32:35 +03:00

Author

Owner

@noisy commented on GitHub (Aug 1, 2019):

Note: as

  -q, --quiet           be quiet, suppress all notices/warnings (implies -y)

option

@noisy commented on GitHub (Aug 1, 2019): Note: as ``` -q, --quiet be quiet, suppress all notices/warnings (implies -y) ``` option

kerem commented

2026-02-25 20:32:35 +03:00

Author

Owner

@aksh7860 commented on GitHub (Aug 1, 2019):

But this doesn't suppress the warning at the start of asciinema

@aksh7860 commented on GitHub (Aug 1, 2019): But this doesn't suppress the warning at the start of asciinema

kerem commented

2026-02-25 20:32:35 +03:00

Author

Owner

@aksh7860 commented on GitHub (Aug 2, 2019):

I mean this -q option do suppress the warnings and notices, but I wanted to suppress the message that is displayed at start and stop of asciinema

@aksh7860 commented on GitHub (Aug 2, 2019): I mean this -q option do suppress the warnings and notices, but I wanted to suppress the message that is displayed at start and stop of asciinema

kerem commented

2026-02-25 20:32:35 +03:00

Author

Owner

@aksh7860 commented on GitHub (Aug 9, 2019):

Hi @sickill @noisy
Can you help here??

@aksh7860 commented on GitHub (Aug 9, 2019): Hi @sickill @noisy Can you help here??

kerem referenced this issue

2026-03-15 08:51:35 +03:00

[GH-ISSUE #92] ctrl-o not working in nano when recording #685