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
hook select crashes #7
Comments
|
Ah, I ran into this issue with my doing project as well. The solution I came up with was to build the fzf binary at runtime, so I'll need to work that functionality into the hook CLI. In the meantime, if you run |
|
Finally got around to updating this with a more robust fzf handler. Please install 2.0.9 ( |
|
Did install 2.0.9. Got error when executing hook: Cause: File mode in hookapp-2.0.9/** not set for group and other. Now hook-cli seems to work. Because fzf is already in my path, I did not test installation helper for fzf. I inspected the files in hookapp-2.0.9: The directory |
|
I think I've fixed the permissions issues in 2.0.10. I ran into a
similar problem with another one of my gems, I think the switch to a new
Mac changed some local permissions without me realizing it.
The helpers directory would be at
$GEM_PATH/gems/hookapp-2.0.10/lib/helpers, but is only be created if it
actually needs to install fzf. If it finds it locally, it should just
use your native copy. Does `hook select FILENAME` work for you now, or
still crashing?
…-Brett
On 28 May 2022, at 2:03, Hanspe-3019 wrote:
Did install 2.0.9. Got error when executing hook:
```
/usr/local/bin/hook:23:in `load': cannot load such file --
/Library/Ruby/Gems/2.6.0/gems/hookapp-2.0.9/bin/hook (LoadError)
from /usr/local/bin/hook:23:in `<main>'
```
Cause: File mode in hookapp-2.0.9/** not set for group and other.
Run `sudo chmod +r ...`
Now hook-cli seems to work. Because fzf is already in my path, I did
not test installation helper for fzf. I inspected the files in
hookapp-2.0.9: The directory `helpers` is missing, so the install
should not succeed anyway.
--
Reply to this email directly or view it on GitHub:
#7 (comment)
You are receiving this because you commented.
Message ID: ***@***.***>
|
|
2.0.10 fixes the permissions issues. |
Running on Intel Core i5:
Can to provide a universal file?
The text was updated successfully, but these errors were encountered: