-
Notifications
You must be signed in to change notification settings - Fork 43
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
Warning/Error reporting not working? #199
Comments
Reading this again, if you have actions to fix unused imports, the warnings would seem to be there. The LSP logs are the only place I would expect to find an issue. Failing that I struggle to see what could be going on, I can't offer any neovim support. Perhaps we can find out if other neovim users see this |
Hi, thanks for your comments! I've reproduced this with what I think is a minimal example with purescript-language-server + nvim-lspconfig + nvim-cmp here, and I captured the verbose log of the problem, and put it at the bottom. Basically I just open a file, get a normal tooltip on
but nothing shows up in the IDE. I do see suggestions for fixing the error, so I know the IDE is aware of it: I did however discover while looking into this that it works just fine in Ubuntu (WSL), but doesn't work on Windows 10! I thought maybe it was my system, but I've uninstalled everything related to neovim (uninstalled all the neovim files in Program Files, the config in AppData\Local\nvim, and the data in AppData\Local\nvim-data) and reinstalled everything and still have the same issue. In other programming languages I do see error messages. Thanks for any information you can give! I understand that this might not get a resolution here.
|
That's interesting, I made an issue a long time ago suggesting there may be some windows path problems and never went anywhere with it. Nobody really confirmed any issue and of course I don't write code on windows. Some suspicious |
Possibly URI normalisation issue, I see |
I appreciate you looking into it! And I'm happy to test anything out. It's weird that it was working regularly for like half a year, and then just stopped. I'm not convinced that it's not related to something weird on my system. Now that I figured out that it works with WSL, the issue is much less of a blocker for me. |
I'm using NeoVim 0.9.0, and this week the highlighting for errors and warnings stopped working, even though the language server is working for other features. I upgraded to version 0.17.2 of the language server, and the broken highlighting seemed to correspond to the upgrade, but the problem persisted after downgrading back to 0.17.1. I can tell the language server is detecting warnings, because if I (for example) add an unused import at the top of the file and open the code actions menu, it will include a suggestion to delete the unused import, it just won't render the warning in any way. The only way I have been able to see errors or warnings is to run
spago build
to see the console output, but autocomplete and other tooltips still show up.I've noticed that VS Code is working as expected (using 0.17.2), but the LSP logs from NeoVim and those from VS Code look identical to me.
I'm out of ideas on what to try to diagnose this any further. Is there any chance that installing 0.17.2 updated some cache or something that remained broken even after downgrading to 0.17.1? I've certainly tried removing the entire .spago/ and output/ folders and rebuilding everything from scratch. Are there any suggestions for what else I can look at to try to get any further information?
The text was updated successfully, but these errors were encountered: