Results 368 comments of rayx

Thanks for submitting the issue. It seems to be caused by the calculation of the floating windows. Could you provide more info reguarding the LSP you using and the function...

The default config in go.nvim (master) gopls.lua ```lua semanticTokens = _GO_NVIM_CFG.lsp_semantic_highlights or false, -- default to false as treesitter is better -- semanticTokenTypes = { keyword = true }, --...

You can add `go.lua` in `lua/snippets` of your config directory and refer to `go.nvim` with `require` some example: https://github.com/ray-x/nvim/tree/master/lua/snippets

With latest lazy.nvim You should be able to use ```lua { 'ray-x/lsp_signature.nvim', event = { 'InsertEnter' }, opts = { ... } } ```

The error you saw was fixed. Also, use the attach method making sure the setup is after lsp_config.

![Image](https://github.com/user-attachments/assets/14ef2ff4-ea98-4117-bc82-8e941850f706) It looks good to me I think there are specific settings in your vimrc affect the background, e.g. gvimrc? ```vim call plug#begin() " List your plugins here Plug 'tpope/vim-sensible'...

I do not have a Debian/Ubuntu box to reproduce this issue. The screenshot is from macvim. Do you enable transparency? `g:aurora_transparent` ?

By default, the scheme supports both ```lua vim.api.nvim_set_hl(0, 'VertSplit', { fg = ct.gray7, ctermfg = 243 }) vim.api.nvim_set_hl(0, 'WinSeparator', { link = 'VertSplit' }) ```