You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 13, 2021. It is now read-only.
How to reproduce
Detailed step to reproduce this issue.
Open a .tex file (and possibly confirm that the texlab language server is connected to buffer)
Type something that triggers completion, for example \begin{
The language server crashes
Expected behavior
A clear and concise description of what you expected to happen.
The language server should not crash.
Okay, I've had quite some struggles with this. At first, I thought this was a bug in texlab because only that language server crashed emmediately after the completion pop up comes. I opened an issue on its repository: latex-lsp/texlab#450. Turns out the language servers receives the following request:
In this, params..textDocument.position.character has a value of -2. This should not be the case (character can not be negative). While going through my configs, it turned out to be that completeopt without noselect causes this! The -2 value is set somewhere around here:
So, TL;DR, language server quits after receiving bad value for position due to completeopt being 'menuone,noinsert'. It works as expected when noselect is added to compleopt.
I'm on the latest nvim (well, updated 5 hours ago) and latest completion-nvim.
Let me know if I could provide more information, happy to help!
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
My testing minimal init.vim
Post your init.vim to help me reproduce this issue
How to reproduce
Detailed step to reproduce this issue.
.tex
file (and possibly confirm that the texlab language server is connected to buffer)\begin{
Expected behavior
A clear and concise description of what you expected to happen.
The language server should not crash.
Okay, I've had quite some struggles with this. At first, I thought this was a bug in texlab because only that language server crashed emmediately after the completion pop up comes. I opened an issue on its repository: latex-lsp/texlab#450. Turns out the language servers receives the following request:
In this, params..textDocument.position.character has a value of -2. This should not be the case (character can not be negative). While going through my configs, it turned out to be that completeopt without noselect causes this! The -2 value is set somewhere around here:
completion-nvim/lua/completion/hover.lua
Lines 352 to 360 in d62fff8
At least, that is where the request comes from.
So, TL;DR, language server quits after receiving bad value for position due to completeopt being
'menuone,noinsert'
. It works as expected whennoselect
is added to compleopt.I'm on the latest nvim (well, updated 5 hours ago) and latest completion-nvim.
Let me know if I could provide more information, happy to help!
The text was updated successfully, but these errors were encountered: