How to make it follow require paths?
#843
Answered
by
mrjones2014
mrjones2014
asked this question in
Q&A
-
|
I have this Neovim config, and ---@type vim.lsp.Config
return {
cmd = { 'emmylua_ls' },
filetypes = { 'lua' },
root_markers = {
'.luarc.json',
'.luarc.jsonc',
'.stylua.toml',
'stylua.toml',
'selene.toml',
'selene.yml',
'.emmyrc.json',
'.git',
},
workspace_required = false,
---@type lsp.emmylua_ls
settings = {
Lua = {
runtime = {
version = 'LuaJIT',
requirePattern = {
'?.lua',
'?/init.lua',
'lua/init.lua',
'lua/?.lua',
'lua/?/init.lua',
'lua/?/?.lua',
'plugin/?.lua',
'ftplugin/?.lua',
'after/?.lua',
'after/?/?.lua',
'spec/?.lua',
},
frameworkVersions = { 'luv' },
},
diagnostics = {
globals = { 'vim' },
},
strict = {
requirePath = false,
},
workspace = {
library = vim.api.nvim_list_runtime_paths(),
},
},
},
} |
Beta Was this translation helpful? Give feedback.
Answered by
mrjones2014
Nov 12, 2025
Replies: 3 comments 8 replies
-
|
see the lsp log in $XDG/emmylua_ls/log/<file_path>.log |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
doesn't seem anything unusual in there as far as I can tell. I redacted paths and replaced with expand for logs |
Beta Was this translation helpful? Give feedback.
-
|
I had my path setup wrong. I needed to wait for my plugin manager to fully setup my lua runtimepath before setting up the LSP. |
Beta Was this translation helpful? Give feedback.
Answer selected by
mrjones2014
-
|
@CppCXY can you please advice about:
with default (empty) If I set {
"runtime": {
"requirePattern": [
"?.lua",
"?/init.lua",
"lua/init.lua",
"lua/?.lua",
"lua/?/init.lua",
"lua/?/?.lua",
"plugin/?.lua",
"ftplugin/?.lua",
"after/?.lua",
"after/?/?.lua",
"spec/?.lua"
],
},
...
"workspace": {
...
library: [
"~/.local/share/nvim/site/pack/core/opt"
],
...
},
...
}(as topicstarter here did), it stops to blame requires of libraries from installed plugins, but starts to blame files in "?/lua/?.lua",
"?/lua/?/init.lua",to the (also, it is strange, that adding patterns stops it from detecting, and not helps)
|
Beta Was this translation helpful? Give feedback.
2 replies
-
|
well, talking on even without making it to see libs from plugins*, if I have only
|
Beta Was this translation helpful? Give feedback.
-
|
well... It seems, I made it to "see" both libs from plugins (don't blame as {
"runtime": {
"requirePattern": [
"?.lua",
"?/init.lua",
"lua/init.lua",
"lua/?.lua",
"plugin/?.lua",
"ftplugin/?.lua",
"after/?.lua",
"after/?/?.lua",
"spec/?.lua"
],
},
"workspace": {
"library": [
"~/.local/share/nvim/site/pack/core/opt"
]
}
}the only things I still can't solve: |
Beta Was this translation helpful? Give feedback.
-
|
@msva |
Beta Was this translation helpful? Give feedback.
4 replies
-
|
For example, you can refer to this library. |
Beta Was this translation helpful? Give feedback.
-
|
well, as for AIs — free AI models (on duck.ai. at least 🤷) either says bullshit (GPT-5) or that they're unfamiliar with emmulua_ls and recommends me to read the readme and ask help from community (Claude Haiku) And as for "gitsigns project" — as far as I can see, it, unfortunatelly, doesn't fit my final questions. Well, I guess when someone develops some project that have some dependencies, they can perform the trick that is used in And as for analysis of the configuration things - I'll try to perform it manually, thanks a lot for the pointer. (although, it still would be very cool if there would be a corresponding README on |
Beta Was this translation helpful? Give feedback.
-
|
You need to use the |
Beta Was this translation helpful? Give feedback.
-
|
Neovim bundles uv by default. Is your Neovim version outdated? see: neovim/neovim#33375 |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I had my path setup wrong. I needed to wait for my plugin manager to fully setup my lua runtimepath before setting up the LSP.