Flag for disabling rendering

[cafkafk]

Is your feature request related to a problem? Please describe.
Over at https://github.com/eza-community/eza we would like to use vhs to do integration testing.

This is possible, but a problem we face is we're not aware of any way to disable generating gif's. We'd like to ideally have a flag that would disable gif generation entirely because:

• It slows down integration tests.
• It simply isn't necessary when we only use Output <something>.txt.

See eza-community/eza#147 for details on usecase.

Describe the solution you'd like
Ideally, a flag for disabling generating and rendering a gif would be sufficient.

This has the advantage of being non-intrusive and breaking to most users, and allowing us to script an option into our build script to include that flag.

Describe alternatives you've considered
Another alternative would be to use a flag that takes a value, which would perhaps be a better solution for scripting like we are doing. But, as a user of this program, I'm not sure it's what I'd prefer UX wise, and I'd rather leave the extra effort to people writing scripts.

Additional context
If there is no one interested in making this, and a potential solution is just adding an option and a if statement somewhere, I could potentially create a PR for this. But I'm stretched a bit thin, and I've never really had a go at go, so I'd prefer not to.

I am aware of the github actions, but we'd really like to do it this way (while also using the github actions, probably).

Also, if there is another, easier and/or obvious way to do this, please let me know :p

[drupol]

This would be also useful for #109

[maaslalani]

Awesome! Thanks for considering using VHS for integration testing. Let me see if I can quickly disable GIF generation for situations when an output is set to text.

[cafkafk]

Awesome! Thanks for considering using VHS for integration testing. Let me see if I can quickly disable GIF generation for situations when an output is set to text.

for eza's use case at least, we've moved pretty far past this solution at this point, so we don't really need it anymore

[drupol]

I would definitely use that new feature.