Closed gunzf0x closed 2 years ago
Are you sure you are on the latest update of AstroVIm, I addressed this problem over here. It did solve the problem for that period.
Yes, I do. I installed AstroVim in this machine last Friday (February 11th, 2022) cloning the repository and applying the packer sync. Also, even if I try :checkhealth telescope
it gives ERROR: No healthcheck found for "telescope" plugin
.
I am experiencing the same issue. First time cloning this project, which is awesome btw, on ubuntu (wsl2 not sure that this information matters)
I found a solution by using nvim-telescope/telescope-fzy-native.nvim
instead of nvim-telescope/telescope-fzy-native.nvim
inside plugins.lua
and then updating line in telescope.lua
to telescope.load_extension "fzy_native"
from telescope.load_extension "fzf"
. Not really sure what are the differences between fzy
and fzf
. Hope this helps đŸ˜„
I had this issue as well. I wish I had been more systematic in my attempts to fix it, but I was just flailing around. I believe I resolved it by uninstalling and reinstalling telescope-fzf-native. I'm guessing I was missing something on the original install that prevented it from compiling. Sorry, I don't have better detail.
I solve the issue by going into the folder of the plugintelescope-fzf-native.nvim
,
and then execute the command make
.
maybe it's because some how the plugin doesn't produce the built file by default?
@moojing for the life of me, I can't find the plugin's folder.
Can you share your path?
EDIT: solution
I solve the issue by going into the folder of the plugin
telescope-fzf-native.nvim
, and then execute the commandmake
.maybe it's because some how the plugin doesn't produce the built file by default?
if make
by itself does not work try make clean
first and then make
from ~/.local/share/nvim/lazy/telescope-fzf-native.nvim
as suggested by this comment
I solve the issue by going into the folder of the plugin
telescope-fzf-native.nvim
, and then execute the commandmake
. maybe it's because some how the plugin doesn't produce the built file by default?if
make
by itself does not work trymake clean
first and thenmake
from~/.local/share/nvim/lazy/telescope-fzf-native.nvim
as suggested by this comment
thank you, it worked <3
For my m3 macbook, go to ~/.local/share/nvim/lazy/telescope-fzf-native.nvim
and run make clean && arch -arm64 make
works well for me.
Hello there!
I'm currently using AstroVim on Ubuntu 20.04 running in WSL2. When I launch AstroVim everything is fine (i.e., it starts without problems). However, when I try to 'Find File' (Space + F + F), for example, I get the error given in the title since some Telescope plugin files are apparently not recognizing 'fzf' extension. This does not break Neovim itself; I can keep using it. But there are some troubles trying to navigate through directories.
To be more specific, this is the exact error:
packer.nvim: Error running config for telescope.nvim: ...er/opt/telescope.nvim/lua/telescope/_extensions/init.lua:10: This extension doesn't exist or is not installed: fzf
This same issue/bug has been reported in LunarVim (which is like AstroVim's cousin): [Bug] This extension doesn't exist or is not installed: fzf #1804
Apparently, the best way to fix this problem is given by this reply (best rated one).
Quoting, it says:
Is there a similar (or different) solution for this issue/bug for AstroVim? Since this issue has appeared a lot in LunarVim and is also present in AstroVim a 'patch' or a solution would be great to improve this Neovim config.
Cheers!