Closed NamelessDev0000 closed 2 months ago
Hey :wave:
this is a haskell-language-server issue, not related to haskell-tools.
You can disable auto_attach
for .hsc
files. See :h haskell-tools.config
.
Hey 👋
this is a haskell-language-server issue, not related to haskell-tools. You can disable
auto_attach
for.hsc
files. See:h haskell-tools.config
.
sry, i can't understand how to use it? it doesn't accept any parameters and seemed to be a const
function...
could you paste a example here?
Hey 👋
this is a haskell-language-server issue, not related to haskell-tools. You can disable
auto_attach
for.hsc
files. See:h haskell-tools.config
.
thx for your reply, successfully solved.
A possible solution:
return {
{
"mrcjkb/haskell-tools.nvim",
config = function()
vim.g.haskell_tools = {
hls = {
auto_attach = function()
local bufnr = vim.api.nvim_get_current_buf()
local filename = vim.api.nvim_buf_get_name(bufnr)
return not filename:match("%.hsc$")
end,
},
}
end,
},
}
Neovim version (nvim -v)
v0.10.0
Operating system/version
Archlinux Rolling
Output of :checkhealth haskell-tools
How to reproduce the issue
Create any
.hsc.
file such this:Expected behaviour
At lease, we should have a option to block such bothering warning rather than let it destroy user's FFI coding experience.
Actual behaviour
Log files
No response
The minimal config used to reproduce this issue.