You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On first install none of the keys work. The Telescope command will be there but the keymaps won't do anything. It'll resolve itself if I quit and reopen.
I checked to see if other plugins did this and I also have neo-tree setup with the keys options like this:
There's indeed a bug here. It's caused by the build part. I'm working on a fix. Due to build, the plugin gets loaded during startup (which is needed), but then when lazy creates lazy handlers, it won't for telescope since that is already loaded.
Can confirm keys are working on first install now!
The only other quick check I made was moving config = function() require("telescope").load_extension("fzf") end back to the fzf-native spec and I still get hit with the error about not finding the "fzf" extension. But it works when I close and reopen.
I'm assuming it has something to do with executing the config before the build command is done.
Did you check docs and existing issues?
Neovim version (nvim -v)
0.9.0
Operating system/version
MacOS Ventura 13.3
Describe the bug
A small annoyance but something I noticed specifically with telescope.
My telescope spec looks like this:
On first install none of the keys work. The Telescope command will be there but the keymaps won't do anything. It'll resolve itself if I quit and reopen.
I checked to see if other plugins did this and I also have neo-tree setup with the keys options like this:
This one works fine on first install though.
Steps To Reproduce
nvim -u repro.lua
nvim -u repro.lua
Expected Behavior
For the keys to work on fist install.
Repro
The text was updated successfully, but these errors were encountered: