Closed cridemichel closed 3 years ago
Please reproduce without additional plugins (you included vimtex in your "minimal" reproduction).
yes indeed vimtex is not necessary to reproduce the problem, I have just edited the first post updating the minimal vimrc file
to reproduce the problem you can open any latex file with the following minimal vimrc file:
From CONTRIBUTING.md:
Write a step-by-step procedure that when performed repeatedly reproduces your issue. If we can't reproduce the issue, then we can't fix it. It's that simple.
Explain what you expected to happen, and what actually happened. This helps us understand if it is a bug, or just a misunderstanding of the behavior.
Create a test case for your issue. This is critical. Don't talk about how "when I have X in my file" or similar, create a file with X in it and put the contents inside code blocks in your issue description. Try to make this test file as small as possible. Don't just paste a huge, 500 line source file you were editing and present that as a test. Minimize the file so that the problem is reproduced with the smallest possible amount of test data.
Can you include an exact test file and tell us exactly what tot type to reproduce the issue including what you expect to happen and what actually happens.
I have just edited my first post including also a minimal latex file to reproduce the issue best C.
thanks, we'll take a look.
thank you
Here's what I see:
RefactorRename
works.GoTo*
commands ever return a location.
2.1. Well, GoToSymbol
and GoToDocumentOutline
do find lines 13 and 15.GetHover
works on arguments of \usepackage
(as in \usepackage{argument}
GetHover
receives null
from texlab on argument of \begin
and \end
. Or anywhere else except 3
.The texlive log is empty. I don't see how this is YCM's fault. Perhaps the user is expected to have some documentation installed?
but as in my first post coc.nvim is able to provide documentation, why?
This repo has nothing to do with coc.vim, so it's not really relevant.
@cridemichel You could have read my guess.
Perhaps the user is expected to have some documentation installed?
You can dive into coc's source and see what it is doing. Or you can ask on the texlive's support channels.
This repo has nothing to do with coc.vim, so it's not really relevant.
thank you very much for pointing it out but I was aware of that, I was just noticing that the coc.nvim is able to provide documentation from the textlab LSP, hence I thought that somehow YCM was failing on this, but if you say that YCM is working properly I believe you, thank you very much for your kindness and support
Doesn't look like our bug. YCM can't do anything with a null response. This question is really for the texlab maintainers.
I noticed that if I add set noshowmode
in the minimal vimrc, which you can find in my first post,
I switch to insert mode and I press "\" (backslash), I get the following error in the command line in red:
AssertionError:
which I presume it is triggered by YCM. Is this also related to texlab?
That's a bug in texlab. https://github.com/latex-lsp/texlab/issues/413
ok thank you again!
@cridemichel
I was just noticing that the coc.nvim is able to provide documentation from the textlab LSP, hence I thought that somehow YCM was failing on this, but if you say that YCM is working properly I believe you
As pointed on latex-lsp/texlab#413. YCM is "working properly" by not having implemented an LSP feature which isn't mandatory, so technically it's at LSP server's fault to not comply with such constrained clients.
If you really wish full LSP support you should go for coc.nvim or nvimlsp anyways, as both started with the mindset of fully supporting LSP, instead of what happened/happens with YCM, which just added/adds LSP as an afterthought.
Issue Prelude
Please complete these steps and check these boxes (by putting an
x
inside the brackets) before filing your issue:vim --version
.:YcmDebugInfo
.:YcmToggleLogs
command.vim -Nu /path/to/YCM/vimrc_ycm_minimal
, including what I expected to happen and what actually happened.install.py
(orcmake
/make
/ninja
) including its invocationThank you for adhering to this process! It ensures your issue is resolved quickly and that neither your nor our time is needlessly wasted.
Issue Details
Dear developers, in latex file if I type "eqnarray" from
coc.nvim
plugin I get the following documentation in a preview popup window:however I get no documentation when using YCM, although from other latex symbols I get something like in the following example:
Actually I am using texlab which I have set up as follows in my .vimrc file:
to reproduce the problem you can open the following latex file
with the following minimal vimrc file:
Diagnostic data
Output of
vim --version
Output of
YcmDebugInfo
Output of
YcmDiags
Output of
git rev-parse HEAD
in YouCompleteMe installation directoryContents of YCM, ycmd and completion engine logfiles