Some language servers like HLS take longer to attach and if we exit
soon before LSP attach had a chance to finish (may be?), server
capabilities field does not seem to be valid in client object and
we get the below error. Check if it valid first.
Error detected while processing LspDetach Autocommands for "*":
Error executing lua callback: /home/core/.config/nvim/lua/lsp.lua:215: attempt to index field 'server_capabilities' (a nil value)
stack traceback:
/home/core/.config/nvim/lua/lsp.lua:215: in function </home/core/.config/nvim/lua/lsp.lua:209>
[C]: in function 'nvim_exec_autocmds'
/usr/local/share/nvim/runtime/lua/vim/lsp.lua:1140: in function </usr/local/share/nvim/runtime/lua/vim/lsp.lua:1139>
Error executing lua callback: /home/core/.config/nvim/lua/lsp.lua:215: attempt to index field 'server_capabilities' (a nil value)
stack traceback:
/home/core/.config/nvim/lua/lsp.lua:215: in function </home/core/.config/nvim/lua/lsp.lua:209>
[C]: in function 'nvim_exec_autocmds'
/usr/local/share/nvim/runtime/lua/vim/lsp.lua:1140: in function </usr/local/share/nvim/runtime/lua/vim/lsp.lua:1139>
Since we now have more mapping available after dropping treesitter
text objects, we can fix this.
Fixes the below warning from targets check health.
targets: health#targets#check
========================================================================
- WARNING: Conflicting mapping found:
aq → <Plug>(textobj-wordcolumn-word-a)
q → {'quote': [{'d': ''''}, {'d': '"'}, {'d': '`'}]}
- WARNING: Conflicting mapping found:
iq → <Plug>(textobj-wordcolumn-word-i)
q → {'quote': [{'d': ''''}, {'d': '"'}, {'d': '`'}]}
The whole bunch of treesitter text objects were difficult to remember
and we ended up rarely ever using any of the defined mappings.
treehopper simplifies things with a single mapping and hints.
We seem to be making a lot of mistakes when it comes to handling
docs/comments in merge requests. Use a more prominent white colour
for the comment highlight group.
Disable logging completely. The set_log_level call needs to be at the
top level else some log message related to startup still gets logged
if the call is done in on_attach.
