Skip to content
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

Command suggestion not work properly: No candidates found #521

Closed
2 tasks done
Tgist1024 opened this issue Feb 15, 2023 · 18 comments
Closed
2 tasks done

Command suggestion not work properly: No candidates found #521

Tgist1024 opened this issue Feb 15, 2023 · 18 comments
Labels
bug Something isn't working has:workaround This issue is not fixed but can be circumvented until then help wanted Extra attention is needed upstream Upstream (neovim/plugin) issues

Comments

@Tgist1024
Copy link

Tgist1024 commented Feb 15, 2023

Version confirmation

  • Confirm

Following prerequisites

  • Confirm

Neovim version

NVIM v0.8.3 Build type: Release LuaJIT 2.1.0-beta3 Compiled by builduser Features: +acl +iconv +tui

Operating system/version

Arch linux 6.1.11

Terminal name/version

kitty 0.27.1

$TERM environment variable

No response

Branch info

main (Default/Latest)

Fetch Preferences

SSH (use_ssh = true)

How to reproduce the issue

  1. Open nvim.
  2. Tab : to input commands.
  3. Try to input something.

Expected behavior

It should work fine.

Actual behavior

No matter what input or not, the suggestion panel just displays No candidates found, and tab completion also doesn't work. If I tried to tab, my input became a single 0.

Additional information

No command input:

image

Input command like help:

image

Before using tab to complete commands:

image

After:

image

checkhealth shows nothing wrong at all

@Tgist1024 Tgist1024 added the bug Something isn't working label Feb 15, 2023
@ayamir
Copy link
Owner

ayamir commented Feb 15, 2023

Can't repo, but you can try :UpdataRemotePlugins

@Tgist1024
Copy link
Author

Tried, but still did not work.

@nkta3m
Copy link

nkta3m commented Feb 15, 2023

I have same error

@nkta3m
Copy link

nkta3m commented Feb 15, 2023

check :messages
nvim-data/site/lazy/wilder.nvim/lua/wilder/internal.lua:4: loop or previous error loading module 'fzy-lua-native'

@Tgist1024
Copy link
Author

Got it, thanks. My error messages have a little different:

..share/nvim/site/lazy/wilder.nvim/lua/wilder/internal.lua:4: in function <...share/nvim/site/lazy/wilder.nvim/lua/wilder/internal.lua:3> function: builtin#18 ...share/n
vim/site/lazy/wilder.nvim/lua/wilder/internal.lua:4: attempt to index a boolean value

It seems to be an upstream error but found no similar issue in wilder.nvim, and that plugin looks like stop developing now.

@ayamir
Copy link
Owner

ayamir commented Feb 15, 2023

Sorry, I can't reproduce it on my machine.
I don't know any better solutions than rm -fr ~/.local/share/nvim/site/lazy/wilder.nvim and then nvim.

@aarnphm
Copy link
Collaborator

aarnphm commented Feb 15, 2023

try

runtime! vim/rtp.vim

UpdateRemotePlugins

@Tgist1024
Copy link
Author

Thanks for all your advice!
I decide to take a while to find an alternative to wilder.nvim because this seems just individual circumstances.

@aarnphm
Copy link
Collaborator

aarnphm commented Feb 15, 2023

I ran intot this issue b4. Maybe it has something to do with using fzf-native-lua. I notice that when I remove the pipeline setup, the error went away.

@HATTER-LONG
Copy link
Contributor

@Tgist1024 I got similar warning, I remove all plugin(rm -rf ~/.local/share/nvim/*) and reload again.
The problem disappears. I think you can try it.

@Tgist1024
Copy link
Author

@Tgist1024 I got similar warning, I remove all plugin(rm -rf ~/.local/share/nvim/*) and reload again. The problem disappears. I think you can try it.

Actually, I have tried this many times before.

@Tgist1024
Copy link
Author

I ran intot this issue b4. Maybe it has something to do with using fzf-native-lua. I notice that when I remove the pipeline setup, the error went away.

It just works! Thank you!

@Jint-lzxy
Copy link
Collaborator

Jint-lzxy commented Feb 15, 2023

This should be an upstream issue. Current workaround is to change return require('.init') in ~/.local/share/nvim/site/lazy/fzy-lua-native/lua/fzy-lua-native.lua to return require('init') (remove that period .).

Looks like this is an issue related to native rtp. Maybe someone will be interested in looking into this weird behavior?

cc @nkta3m @HATTER-LONG @Tgist1024 @Yan-weihao @aarnphm

@Jint-lzxy Jint-lzxy added help wanted Extra attention is needed has:workaround This issue is not fixed but can be circumvented until then upstream Upstream (neovim/plugin) issues labels Feb 15, 2023
@Yan-weihao
Copy link

This should be an upstream issue. Current workaround is to change return require('.init') in ~/.local/share/nvim/site/lazy/fzy-lua-native/lua/fzy-lua-native.lua to return require('init') (remove that period .).

Looks like this is an issue related to native rtp. Maybe someone will be interested in looking into this weird behavior?

cc @nkta3m @HATTER-LONG @Tgist1024 @Yan-weihao @aarnphm
Screenshot_2023-02-16-02-55-12_1920x1080
I am surprised that there is nothing in this file of mine

@Yan-weihao
Copy link

This should be an upstream issue. Current workaround is to change return require('.init') in ~/.local/share/nvim/site/lazy/fzy-lua-native/lua/fzy-lua-native.lua to return require('init') (remove that period .).这应该是一个上游问题。当前的解决方法是将 ~/.local/share/nvim/site/lazy/fzy-lua-native/lua/fzy-lua-native.lua 中的 return require('.init') 更改为 return require('init') (删除句点 return require('.init'))。

Looks like this is an issue related to native rtp. Maybe someone will be interested in looking into this weird behavior?看起来这是与原生 rtp 相关的问题。也许有人会对调查这种奇怪的行为感兴趣?

cc @nkta3m @HATTER-LONG @Tgist1024 @Yan-weihao @aarnphm

I re-installed this plug-in, and now it has worked, thanks for your reminding,
Screenshot_2023-02-16-03-00-25_1920x1080

@CharlesChiuGit
Copy link
Collaborator

I got the same issue after update lazy.nvim.

Looks like this is an issue related to native rtp. Maybe someone will be interested in looking into this weird behavior?

I think the reason is that lazy clear the rtp for faster startup hence causing the issue.

@CharlesChiuGit
Copy link
Collaborator

I have create a tmp fork and submit a PR to fzy-lua-native.

Others can use this tmp fork for now if u don't want to edit the file.
https://github.com/CharlesChiuGit/fzy-lua-native

@CharlesChiuGit
Copy link
Collaborator

CharlesChiuGit commented Feb 16, 2023

lazy.nvim v9.8.3 fixes this issue. ref: folke/lazy.nvim#543 epwalsh/obsidian.nvim#93
close the issue for now. fell free to reopen it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working has:workaround This issue is not fixed but can be circumvented until then help wanted Extra attention is needed upstream Upstream (neovim/plugin) issues
Projects
None yet
Development

No branches or pull requests

8 participants