-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when auto-completion fires: wrong-type-argument arrayp nil #31
Comments
@xianghx I fixed that with |
That is covered by |
Which is the problem I'm reporting :) |
Lenguajes de programación afectados: - Python - Golang - Java - JavaScript - TypeScript - PHP - C++ - Rust Existe una falla en company-lsp que previene el uso de lsp por el momento, hay que esperar hasta que la falla company-lsp#31 sea arreglada. - https://christian.kellner.me/2017/05/31/language-server-protocol-lsp-rust-and-emacs/ - https://code.visualstudio.com/blogs/2016/06/27/common-language-protocol - tigersoldier/company-lsp#31
Sorry for late response. For lsp-go: The go language server doesn't provide completion support. You can confirm it by For lsp-python: It's unclear what went wrong. It's likely a bug in the code. I tried on my machine and it works well. Can you provide the following information for further debugging?
|
Sorry I missed comment about emacs-lsp/lsp-go#6 With that patched I was able to trigger completion for Go. I managed to trigger the error Are you constantly triggering this issue? There may be a bug on the lsp-mode side or go/python language server side. company-lsp can provide better messaging but cannot help with the root cause. |
Well, I think this is something related to lsp-mode because I was able to reproduce the exact same error in php-mode and js2-mode (both switched on *scratch* buffer). Vue-lsp works fine, the auto-completion suggestion seems not related to what you write (It may be a thing of the server) and other features of lsp works too: When I open a Javascript file, the auto-completion works fine in js2-mode: The error still happens for python-mode in a project that had no Isn't there a way to spy the communications between lsp-mode and the servers? that would help a lot for bug reporting. |
Note this: Another unrelated package called importmagic experiences the exact same error:
|
Sorry, didn't saw that reply that was before your last reply. Will provide that information soon
El 9 de abril de 2018 12:15:23 AM CST, Caibin Chen <notifications@github.com> escribió:
…Sorry for late response.
For lsp-go: The go language server doesn't provide completion support.
You can confirm it by `M-x lsp-capabilities`.
For lsp-python: It's unclear what went wrong. It's likely a bug in the
code. I tried on my machine and it works well. Can you provide the
following information for further debugging?
1. Before opening any python file, `M-x set-variable RET lsp-print-io
RET t`
2. Open the problematic Python file, try completion
3. Paste the content of the `*Messages*` buffer here
4. Run `M-x copmany-diag` in the Python file with cursor after a dot,
and paste the content of company-diag output here.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#31 (comment)
--
Enviado desde mi dispositivo Android con K-9 Mail. Por favor, disculpa mi brevedad.
|
Here is the information you requested. With
Then I position the cursor after the dot and call to
Despite |
I said before that js2-mode worked fine with lsp-mode, it turns out tide-mode was providing the auto-completion at that time. If I turn off tide-mode and restart Emacs and try again auto-completion in js2-mode fails as well as in Python and the other programming languages. |
Lenguajes de programación afectados: - Python - Golang - Java - JavaScript - TypeScript - PHP - C++ - Rust Existe una falla en company-lsp que previene el uso de lsp por el momento, hay que esperar hasta que la falla company-lsp#31 sea arreglada. - https://christian.kellner.me/2017/05/31/language-server-protocol-lsp-rust-and-emacs/ - https://code.visualstudio.com/blogs/2016/06/27/common-language-protocol - tigersoldier/company-lsp#31
I ran bug-hunter in my configuration, and this was the result:
I decided to bisect further by setting |
I experienced the bug reported on #17
This has happen on Go and Python, and I expect to happen on other languages too.
After inserting the dot to fire auto completion with Company, it fails: nothing happens.
toggling debugging on error on reveals the following (python-mode running on the *scratch* buffer):
This is my current configuration:
The text was updated successfully, but these errors were encountered: