Where to check Lua runtime search path sources?

[dasupradyumna]

How are you using the lua-language-server?

NeoVim

Which OS are you using?

Linux

What is the issue affecting?

Other

Expected Behaviour

I encountered a weird issue while setting up my NeoVim lua configuration. In a file which configures "nvim-dap" plugin, I import using require 'dap'. But the server detects another file named dap.lua in a different plugin folder which, as far as I know, is not on the runtime search path. This ends up giving me the wrong completions and suggestions, since it is loading the wrong file / table. The desired table is the second suggestion in the list.

I expect the server to output the second file as the first option, since it is in a standard runtime path, as seen in the image below.

Actual Behaviour

As you can see, the second (correct) result's search path is standard, whereas first result's search path is unexpected.

I wanted to know if there is any way I can check where these search paths are sourced from, because I did not provide any such path lua/mason/ui/components/help/?.lua in my config. The language server works flawlessly except for this problem.

Reproduction steps

• I just triggered the go to definition on the word under the cursor.

Additional Notes

No response

Log File

No response

[sumneko]

Use setting runtime.pathStrict

[dasupradyumna]

Hey, thanks for the reply.
I have tried using the setting you suggested, and it solved my problem i.e, the LSP now shows the correct hover and autocompletion suggestions on the imported local variable and its members. But it has introduced a new problem, I am not able to use "go to definition" or "hover" on the require 'dap' or any other import.

In my config, workspace.library setting is the ouput of vim.api.nvim_get_runtime_file('', true), so the workspace library has access to all the plugin files, but can no longer populate them in suggestions.

[AbaoFromCUG]

ouput of vim.api.nvim_get_runtime_file('', true), so the workspace library has access to all the plugin files, but can no longer populate them in suggestions.

I address this issue via runtime.path, here is my configuration

local config = {
	settings = {
		Lua = {
			runtime = {
				-- LuaJIT in the case of Neovim
				version = "LuaJIT",
				pathStrict = true,
				path = {
					"lua/?.lua",
				},
			},
			workspace = {
				-- Make the server aware of Neovim runtime files
				library = vim.api.nvim_get_runtime_file("", true),
				checkThirdParty = false,
			},
		},
        --... some other settings
	},
}````

[memchr]

Would it be a good idea to have a section in the FAQ dealing with this quirk when using luals with neovim lua configuration? This seems to be a common problem.