Find word not working

[Dennis-Zhang-SH]

Hi, I am a newbie to vim and neovim, I was using vs code mostly in the past, and I just began to use this neovim setting, it's blazing fast and easy to use, but I wonder why that space f f works fine on searching files, but space f w failed to search and return with a warning.

Directly using grep_string return with an not found libtelescope.so error, should I install it?

[CharlesChiuGit]

I think telescope.nvim might not install successfully. I would suggest remove it from the plugin folder and re-open nvim to let lazy.nvim re-install it again.
If the error persist, show us some screenshots and the error log.

[Dennis-Zhang-SH]

Hi I reinstall it, and the result is in the following:

space fw not working

space ff works fine

[Jint-lzxy]

Hi @Dennis-Zhang-SH first you need to install a patched font in order to render the icons correctly.

About your question, do you have all the necessary dependencies installed according to Wiki:Prerequisites#required-packages-installation? BurntSushi/ripgrep is required for live_grep and grep_string.

[CharlesChiuGit]

Hmmm, this seems like a upstream bug, related to nvim-tree and https://github.com/ahmedkhalf/project.nvim.
I think this should be filed in new issue in this repo, maybe u can search for upstream repos to find some useful infos if possible.

[Dennis-Zhang-SH]

Command failed

Sure, one last question, how could I find out the lsp prompt? Like in the vscode, you could always navigate to problems tab in the terminal window, which would be very convenient.

[CharlesChiuGit]

I not sure what u mean, I haven't use vscode for coding in a very long time. But maybe this is what u need?

nvimdots/lua/keymap/completion.lua

Lines 12 to 13 in ed54fd6

	["n|g["] = map_cr("Lspsaga diagnostic_jump_prev"):with_noremap():with_silent():with_desc("lsp: Prev diagnostic"),
	["n|g]"] = map_cr("Lspsaga diagnostic_jump_next"):with_noremap():with_silent():with_desc("lsp: Next diagnostic"),

or

nvimdots/lua/keymap/tool.lua

Lines 84 to 102 in ed54fd6

	-- Plugin: trouble
	["n|gt"] = map_cr("TroubleToggle"):with_noremap():with_silent():with_desc("lsp: Toggle trouble list"),
	["n|<leader>tr"] = map_cr("TroubleToggle lsp_references")
	:with_noremap()
	:with_silent()
	:with_desc("lsp: Show lsp references"),
	["n|<leader>td"] = map_cr("TroubleToggle document_diagnostics")
	:with_noremap()
	:with_silent()
	:with_desc("lsp: Show document diagnostics"),
	["n|<leader>tw"] = map_cr("TroubleToggle workspace_diagnostics")
	:with_noremap()
	:with_silent()
	:with_desc("lsp: Show workspace diagnostics"),
	["n|<leader>tq"] = map_cr("TroubleToggle quickfix")
	:with_noremap()
	:with_silent()
	:with_desc("lsp: Show quickfix list"),
	["n|<leader>tl"] = map_cr("TroubleToggle loclist"):with_noremap():with_silent():with_desc("lsp: Show loclist"),

[CharlesChiuGit]

Personally I don't think it's necessary to replicate every function in vscode, we can just done the same thing in different way. So maybe next time u can describe what exactly u want to achieve instead of describing a function in vscode. Abstract the concept.

[Dennis-Zhang-SH]

Personally I don't think it's necessary to replicate every function in vscode, we can just done the same thing in different way. So maybe next time u can describe what exactly u want to achieve instead of describing a function in vscode. Abstract the concept.

Oh it's the <leader>tw, thanks, sure I would describe the concept next time, I am too familiar with vscode, sorry about that.

[Dennis-Zhang-SH]

Thanks for all the help, I think I could start using my neovim journey :).