This repository has been archived by the owner on Jun 8, 2023. It is now read-only.
Tooltips and autocomplete do not work #36
Comments
|
Did you notice anything unusual in the log file ( |
|
Yes: |
|
I update Esimite to the latest version in plugins.sbt and it started to work:
However, a half of tooltips are empty:
|
|
Also, it does not show red squiggles if code is not compilable. |
|
Yes, indeed.. Unfortunately the Ensime API is limiting, and it provides hover information only for class members. I had tried a few different things here, still both implementations are there. One can return the type, but that has no proper |
|
I see, thanks. What about error highlighting? Is it supposed to work? |
|
Yes, it's supposed to work. I'm wondering if there's an error somewhere along the lines. CMD-Shift-M should show all errors that are reported by the language server. Do they appear there? I'm wondering if the initial crashes still happen, and if they have anything to do with it. I noticed such moments with no red squigglies, but couldn't reproduce reliably to debug them. |
|
No, the errors window shows nothing:
This is the complete log (no tooltips or completions performed, just opened a file and wait for CPU becomes idle): |
|
I see, it's weird. Ensime reports the errors, but they get lost somewhere along the way, maybe the URI used to identify the file is screwed up, most likely a Unix-style assumption on my part that doesn't work with Windows paths. Most likely line is this one |
|
I'm behind a proxy here, may it cause the problem? I'll test it at home (no proxy). |
|
I get the same lack of squiggles and problem logging on a Windows setup. I'll have to wait a couple of weeks to try on macOS. |
|
It'd be great to have a fix for Windows users, if anyone here is motivated and is a Windows user. |
|
I'm only using Windows for a temporary period, but have chucked a pull request up for the diagnostic reporting: #42 |
|
If it helps, I am having similar problems on NixOS, which is a Linux system but based on the rather unconventional Nix package manager; so this does indeed point to overly specific path assumptions. |
|
By the way, https://github.com/dragos/dragos-vscode-scala/pull/42/files got merged, so this should be fixed now. @ixxie Can you confirm? |
|
@ixxie the releases tab is lying. The latest release is from June 20 and includes that fix. I don't know why GitHub is confused. Tags look good though. |
|
It just collapses latest tags. You have to explicitly create Github release based on a tag for it to be visible in the Releases tab. In case you want to automize it (publishing release notes as Github Releases), there's a plugin (that I'm maintaining): sbt-github-release |
|
@dragos - the latest release doesn't seem to include the .vsix, so I would still have to build it (as I said, I can do this eventually, but not quite now). |
|
@ixxie can't you just install it from the Marketplace? The Releases GitHub page isn't necessary nor useful here :) |
|
@ixxie I don't know what version you have and why you have difficulties upgrading, but the version on the marketplace is 0.1.6. It should upgrade like any other extension. |
|
@dragos it seems to be up to date (for some reason, VSCode doesn't show version number of the extension explicitly, but it doesn't seem to think the extension needs to be updated). So either this fix doesn't work on NixOS, or I am still doing something else wrong on my end. |
|
This is how my Extensions page looks, and the version number is there. |
|
Oops. Missed that. Hmmm 1.1.2, and uninstalling / reinstalling doesn't help. This has to be something on my end, maybe my VSCode is out of date or something. Will look into it. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The text was updated successfully, but these errors were encountered: