Replies: 1 comment 1 reply
-
|
Does the regular I've previously introduced this file path resolving strategy, but thought it was only needed on Windows: CliWrap/CliWrap/Command.Execution.cs Lines 17 to 75 in fdf4bce |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I am trying to call
whisper-ctranslate2that I installed on Debian 13 using pipx, and I get an exception that the exe was not found.I install like this:
sudo apt install ffmpeg python3 python3-pip python3-venv build-essential pipx pipx ensurepath pipx install whisper-ctranslate2 pipx list which whisper-ctranslate2 command -v whisper-ctranslate2 whisper-ctranslate2 --helpThis works fine, and when I SSH remove VSCode to the machine it also works fine when called from the VSCode terminal:
$ which whisper-ctranslate2 /home/pieter/.local/bin/whisper-ctranslate2 $ command -v whisper-ctranslate2 /home/pieter/.local/bin/whisper-ctranslate2 $ whisper-ctranslate2 --help usage: whisper-ctranslate2 [-h]And the "executable"
/home/pieter/.local/bin/whisper-ctranslate2is a shell redirection:When I call CliWrap with just the
whisper-translate2, I get:To fix it I must explicitly call the absolute path:
This makes it machine and user specific, how can I call the "executable" in the same way the shell would call it without needing to create an absolute path?
Beta Was this translation helpful? Give feedback.
All reactions