On Windows, vhs records inside a WSL bash session rather than the shell it was invoked from. A consequence: commands available in the invoking terminal (Git Bash/PowerShell PATH) aren't necessarily available inside the recording — e.g. a tape that runs vhs validate printed bash: vhs: command not found even though vhs was on PATH in the terminal that launched the render.
This may be entirely expected (different OS context), but it's surprising the first time and costs a debugging cycle. If it's working as intended, a short note in the README's Windows section ("recordings run in your default WSL distro; install the tools you want to demo inside WSL") would save people the confusion. Happy to PR that note if useful.
Environment: vhs 0.11.0 via winget, Windows 10 (10.0.19045), WSL Ubuntu 24.04.
On Windows, vhs records inside a WSL bash session rather than the shell it was invoked from. A consequence: commands available in the invoking terminal (Git Bash/PowerShell PATH) aren't necessarily available inside the recording — e.g. a tape that runs
vhs validateprintedbash: vhs: command not foundeven though vhs was on PATH in the terminal that launched the render.This may be entirely expected (different OS context), but it's surprising the first time and costs a debugging cycle. If it's working as intended, a short note in the README's Windows section ("recordings run in your default WSL distro; install the tools you want to demo inside WSL") would save people the confusion. Happy to PR that note if useful.
Environment: vhs 0.11.0 via winget, Windows 10 (10.0.19045), WSL Ubuntu 24.04.