Closed ravibrock closed 7 months ago
Not sure if it is related to the old bug (https://github.com/nvim-telescope/telescope.nvim/issues/2501) reported in telescope.nvim. At least it can be a reference. Also, this one https://github.com/nvim-telescope/telescope.nvim/issues/2766 maybe helpful to track.
Yep, that worked to fix it. Thank you for the help!
Would you be able to say if that is expected behavior for the lsp
folding option? I can also open another issue for that if it would work better, but it seemed very minor.
Selected provider
should show lsp
instead of indent
. I think the issue is caused by the lazy loading of lazy.nvim. I don't use lazy.nvim so I have no hints. Seems it's not attached normally. Probably the event should be BufRead
instead of BufReadPost
. Hmm, I don't know. Check this https://github.com/kevinhwang91/nvim-ufo/issues/117 that might be useful.
Ok, I got it working now. Thank you for all the help! Turns out the issue was how the language servers were being configured - I fixed it in my mason-lspconfig
setup.
Neovim version (nvim -v | head -n1)
NVIM v0.9.4
Operating system/version
MacOS 14.1.1
How to reproduce the issue
Lazy.nvim:
Nvim-ufo config:
Alpha config:
I install the plugins with Lazy.nvim as shown above, and then they each source the code I have listed below for configuration.
Expected behavior
I would expect to enter buffers from telescope in normal mode rather than in insert mode. I would also expect
:UfoInspect
to saybut as I said, I could be mistaken on this.
These aren't huge issues, so it's not a big rush. Any help is appreciated. Thank you!
Actual behavior
I noticed that when I type, for example,
r
on my Alpha dashboard (to search recent files as indicated in the config), it enters the selected recent file's buffer in insert mode when I'm lazy-loading nvim-ufo onBufReadPost
andBufNewFile
but not when I load it eagerly.I also noticed, when debugging this, that
:UfoInspect
always sayswhen on a file that should be using a LSP. I would think that it should be
Selected provider: lsp
but I could be mistaken. My config for the LSP is in the example as well.