-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: binary not found: cannot find binary path #4
Comments
Hi jediaxe,
I'm currently on vacation without keyboard and will return on 07th January, until then you can try several things:
- set the RUST_BACKTRACE=1 env flag to find the problematic function
- install latex, gnuplot, ImageMagick
Probably some binary is missing, though you do not require them. When I'm back (and you have not created a patch) I will debug further.
Cheers,
Lorenz
25.12.2022 11:14:07 jediaxe ***@***.***>:
… First thank you for this wonderful plugin! inline images functionality is the only thing missing in Vim. judging from the sample videos, vim-graphical-preview makes Vim a better file viewer with true inline images unlike other available options that utilize search and pop-up solutions etc.
I have followed the installation guide and plugins were installed correctly along with all dependencies including rust stable toolchain.
however I can't get it to work.
vim: set filetype=graphical-preview : wont load any images
vim: set filetype=markdown.graphics : Vim displays Error: binary not found: cannot find binary path.
I made sure the correct path for rust is set in zshrc export PATH="$HOME/.cargo/bin:$PATH" and tried all other PATH methods just incase (.zshenv) (.profile) and (~/.cargo/env) etc.
I have also tried installing rustup from the Arch repository and manually using the link from the installation guide (with rustup from the Arch repository executables live in /usr/bin, instead of ~/.cargo/bin)
Tested using a bare bones vim without any options or plugins other than the two mentioned in the installation guide.
Tested With and without tmux.
I managed to get image preview working just fine in vifm using vifmimg[https://github.com/cirala/vifmimg]
Terminal: Alacritty
Am I missing something? how can I get it to work?
—
Reply to this email directly, view it on GitHub[#4], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AAHRRKJWDY6XLRAX4SHDWYTWPAM6TANCNFSM6AAAAAATI5E2KU].
You are receiving this because you are subscribed to this thread.[Verfolgungsbild][https://github.com/notifications/beacon/AAHRRKLYBIOQ7JGUZ3ZMUL3WPAM6TA5CNFSM6AAAAAATI5E2KWWGG33NNVSW45C7OR4XAZNFJFZXG5LFVJRW63LNMVXHIX3JMTHFUBKAAE.gif]
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
First thank you for this wonderful plugin! inline image functionality is the only thing missing in Vim. judging from the sample videos, vim-graphical-preview makes Vim a better file viewer with true inline images unlike other available options that utilize search and pop-up solutions etc.
I have followed the installation guide and plugins were installed correctly along with all dependencies including rust stable toolchain.
however I can't get it to work.
vim: set filetype=graphical-preview : wont load any images
vim: set filetype=markdown.graphics : Vim displays Error: binary not found: cannot find binary path.
I made sure the correct path for rust is set in .zshrc export PATH="$HOME/.cargo/bin:$PATH" and tried all other PATH methods just incase (.zshenv) (.profile) and (~/.cargo/env) etc.
I have also tried installing rustup from the Arch repository and manually using the link from the installation guide (with rustup from the Arch repository executables live in /usr/bin, instead of ~/.cargo/bin)
Tested using a bare bones vim without any options or plugins other than the two mentioned in the installation guide.
Tested With and without tmux.
I managed to get image preview working just fine in vifm using vifmimg
Terminal: Alacritty
Am I missing something? how can I get it to work?
The text was updated successfully, but these errors were encountered: