Code actions unavailable with Emacs' lsp-mode
See original GitHub issueInfo
- Platform: Linux
- Vetur version:
- VS Code version: 1.49.1
- Editor: Emacs
Problem
When using Emacs with lsp-mode, I try to call code actions, but it spams error messages like:
LSP :: Error from the Language Server: Request textDocument/codeAction failed with message: Cannot read property 'codeActions' of undefined (Internal Error)
Found in lsp-mode logs:
[Trace - 10:36:52 AM] Received response 'textDocument/codeAction - (48)' in 61ms.
Result: null
When using VSCode, this or a similar error message doesn’t appear, but code actions are still unavailable, including when opening the veturpack sample project
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Code actions unavailable with Emacs' lsp-mode #2355
IssueHunt = OSS Development ⚒ + Bounty Program . IssueHunt is an issue-based bounty platform for open source projects. Anyone can put a...
Read more >emacs-lsp/lsp-mode - Gitter
Is there a way to disable a specific code action from showing up in the list of possible code actions? In particular, when...
Read more >LSP Mode code completion not working : r/emacs
I've installed lsp-mode and am having trouble getting code completion working for PHP. I tried https://emacs-lsp.github.io/lsp-mode/page/lsp-php/ and…
Read more >Emacs LSP mode - is it possible to avoid mouse click ...
Are you seeing in the minibuffer a list of possible code actions and you want to know how to select one with the...
Read more >Emacs From Scratch #8 - Build Your Own IDE with lsp-mode
This time we'll be learning how to build a modern coding experience similar to Visual Studio Code and JetBrains IDEs with Emacs '...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
emacs-lsp/lsp-mode@46d1a7e4029fb141d41504095e0e10741c7fb624 seems to fix it. Gonna check and report back.
The error is gone. Closing the issue, turns out it wasn’t on the side of Vetur.