-
Notifications
You must be signed in to change notification settings - Fork 156
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
Intellisense broken for default VScode quick suggestion delay. #805
Comments
I won't be able to attempt to repro on my windows machine for a while, but you could be hitting path normalization errors like has been discussed in #800. One thing that would be helpful is to enable |
Sorry, I think you misunderstood me a bit. Verbose logging at the FSAC level was turned on, yes, but I was asking you to turn on the LSP-level logging via this new key. That would actually let us see the LSP calls that are driving the experience you're seeing. |
You can always add the option in the setting.json manually. We don't advertise it because it's an implementation detail of vscode. In general you can do LANGUAGENAME.trace.server and vscode will start tracing. |
OHHHH, I see. Okay here we go, sorry about that :). |
That was me doing the same stuff as in the gif, I wrote just one letter. and it triggered and failed. I wrote two letters before the popup and it worked fine. I was able to have it work fine by starting the intellisense on a partially written word (with at least 2 letters). |
Oh I just noticed if I trigger the intellisense using |
Okay, I've just started to have to do f# coding again and this problem is driving me mad. (Happening on both windows and linux) I spent all of today going through FSAC trying to pin down why it is happening with little success.
My conclusion at this point is that there is something about making a change to the file that clears the cached typecheck results and they then get regenerated very shortly after. This is why adjusting your delay for the quick suggestions popup solves the problem. |
Fixed in |
Recently (last few weeks) something has broken for me in Ionide vscode.
This happens on my 3 different windows machines.
Instead of getting intellisense suggestions. Nothing happens.
I can trigger it sometimes by typing part of the desired word
say "prin"
deleting some
"pr"
Then the popup appears sometimes.
I had a problem like this once before and fixed it by turning up the quick suggestion delay.
If I turn up the delay and make sure that I type more than 2 letters before the popup triggers it will work
Here is the complete log from the F# output in vscode.
log.log
That was all fresh f# project. "dotnet new console -lang f#"
Hopefully this is sufficiently reproduceable and detailed #802 😄
The text was updated successfully, but these errors were encountered: