artemave / workspace-diagnostics.nvim

Populate diagnostics for _all_ projects files, not just opened ones.
https://artem.rocks/posts/workspace_diagnostics_nvim
MIT License
143 stars 4 forks source link

Vim:E976: Using a Blob as a String #6

Closed adelarsq closed 6 months ago

adelarsq commented 6 months ago

Description

These errors appears when open any TypeScript file using the default tsserver config:

   Error  10:40:52 msg_show.lua_error LSP[tsserver]: Error ON_ATTACH_ERROR: "BufEnter Autocommands for \"*\": 
Vim(append):Error executing lua callback: Vim:E976: Using a Blob as a String\nstack traceback:\n\t[C]: in function 
'match'\n\t...hlight-colors/lua/nvim-highlight-colors/buffer_utils.lua:21: in function 'get_positions_by_regex'\n\t...nvim-highlight-
colors/lua/nvim-highlight-colors/init.lua:59: in function 'highlight_colors'\n\t...nvim-highlight-colors/lua/nvim-highlight-
colors/init.lua:88: in function 'refresh_highlights'\n\t...nvim-highlight-colors/lua/nvim-highlight-colors/init.lua:137: in function 
<...nvim-highlight-colors/lua/nvim-highlight-colors/init.lua:135>\n\t[C]: in function 'bufload'\n\t...pace-
diagnostics.nvim/lua/workspace-diagnostics/init.lua:60: in function '_detect_filetype'\n\t...pace-diagnostics.nvim/lua/workspace-
diagnostics/init.lua:77: in function '_get_filetype'\n\t...pace-diagnostics.nvim/lua/workspace-diagnostics/init.lua:107: in function 
'populate_workspace_diagnostics'\n\tC:\\Users\\adelar.queiroz\\AppData\\Local\\nvim\\init.lua:368: in function 
'_on_attach'\n\t.../nvim-data/lazy/nvim-lspconfig/lua/lspconfig/configs.lua:278: in function '_setup_buffer'\n\t.../nvim-
data/lazy/nvim-lspconfig/lua/lspconfig/configs.lua:234: in function <.../nvim-data/lazy/nvim-
lspconfig/lua/lspconfig/configs.lua:232>\n\t[C]: in function 'pcall'\n\tC:/dev/nvim-
win64/share/nvim/runtime/lua/vim/lsp/client.lua:536: in function '_run_callbacks'\n\tC:/dev/nvim-
win64/share/nvim/runtime/lua/vim/lsp/client.lua:947: in function 'on_attach'\n\tC:\\dev\\nvim-
win64\\share\\nvim\\runtime/lua/vim/lsp.lua:397: in function <C:\\dev\\nvim-
win64\\share\\nvim\\runtime/lua/vim/lsp.lua:387>\n\t[C]: in function 'pcall'\n\tC:/dev/nvim-
win64/share/nvim/runtime/lua/vim/lsp/client.lua:536: in function '_run_callbacks'\n\tC:/dev/nvim-
win64/share/nvim/runtime/lua/vim/lsp/client.lua:611: in function 'fn'\n\tvim/_editor.lua:350: in function <vim/_editor.lua:349>"

Steps to reproduce

  1. Follow the default config for the plugin
  2. Add default tsserver config:
function _G.my_on_attach(client, bufnr)
    local opts = { noremap = true, silent = true }

    require("workspace-diagnostics").populate_workspace_diagnostics(client, bufnr) -- add behavior here
end

local getLspCapabities = function()
    local my_capabilities = require('cmp_nvim_lsp').default_capabilities()

    my_capabilities.textDocument.foldingRange = {
        dynamicRegistration = false,
        lineFoldingOnly = true
    }
    return my_capabilities
end

local my_capabilities = getLspCapabities()

local lspconfig = require('lspconfig')

lspconfig.tsserver.setup({ on_attach = _G.my_on_attach, capabilities = my_capabilities })
  1. Error. It shows the messages and ignore any default config for the LSP server. For tsserver for example, it forgets to add tsconfig.json .

Expected behavior

No error.

Environment

adelarsq commented 6 months ago

Closing since its a bug on nvim-highlight-colors that causes a missbehaviour on this plugin.