How to get lua-language-server to detect the filetype of the scratch pad

[michaelfortunato]

Hi! First off, huge fan of this plugin. This is the best scratchpad plugin by far.
One question, how do I get my lua language server to operate on the buffer?

[YaroSpace]

Hi! Very glad you like it.

Lua_ls should be working in the console without any setup.

Is it working in a lua file?

[mortalapeman]

I am using neovim version v0.11.4 and the Lua_ls does not appear to be attached to the scratch buffer. Granted, I am exceptionally new to plugin development and I was trying to use lua-console for exploring the API. If check LspInfo to see which buffers the LSP is attached to, it shows the lua files I have manual opened to edit, but none of the hidden buffers (including the scratch buffer) that I have to display with :ls!.

It does seem to work if I attach it to a lua file, but the eval sometimes dumps text directly to the buffer and sometimes evals as virtual text. I would prefer the plugin not dump output text into my working file, so I was trying out the lua console and found the LSP to not work.

If there are any commands I could run to help diagnose the issue I would be happy to do that. In the mean time, I'll work on figuring out how to debug all of this.

[YaroSpace]

One line results are shown as virtual text, multi line are appended to the attached buffer/console.

Lua_ls should attach automatically to any lua filetype buffer, including the console. But lua_ls can take some time to start, especially if you have extra indexing paths added in the lua_ls.Lua.runtime.path opts of the lsp config or if using lazydev plugin.

[mortalapeman]

I am using using the base kickstart nvim config, so maybe there is something in there that is wrecking havoc with your plugin. If I try to show docs for vim.cmd in the lua console I get the "man.lua: no manual entry for cmd" error.

Autocomplete works in lua files, just not in the lua console.

I wiped out all my buffers with %bw then pressed ` to open the lua console. Here is the result of LspInfo

The result of :ls!

Considering I only have the 1 buffer with a lua file type I would have expected the LSP to attach to it. I will try and narrow down my kickstart config to something minimal and see if I can isolate the issue.

Is it because the LSP is only attached to the .config/nvim directly and the lua console file is in .local/share?

[YaroSpace]

usually the config of a lsp server sets up an autocommand triggered on filetype, that starts a lsp client for the buffer. It is not happening in your case for lua-console for some reason.

Try starting it manually with :LspStart lua_ls while in the console.

Also, let me have look at your kickstart config, maybe I can see an issue.

[mortalapeman]

I tried running :LspStart lua_ls while in the console and nothing appeared to happen. The lack of autocomplete remained. Here is my current kickstart config:

https://github.com/mortalapeman/kickstart.nvim

I haven't changed too much from the base config. When I get some time I'll work on debugging the issue, but I appreciate your willingness to look into it.

[YaroSpace]

Aha, found the issue. The LSP attach sequence changed slightly. Pushed a fix.