Skip to content
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

Module autocompletion occasionally duplicates one of the segments #342

Closed
ProofOfKeags opened this issue Aug 20, 2020 · 1 comment
Closed
Labels
component: ghcide type: bug Something isn't right: doesn't work as intended, documentation is missing/outdated, etc..

Comments

@ProofOfKeags
Copy link

Environment: VSCode

Release 0.3.0

tested module imports from fused-effects

Importing Control.Car<tab> results in Control.Carrier.Empty.Church <- this is correct
Importing Control.Carrier.E<tab> results in Control.Carrier.Carrier.Empty.Church
Importing Control.Carrier.Empty.C<tab> results in Control.Carrier.Empty.Empty.Church

This is stable across packages.

Hitting '.' the after the first segment kills the autocomplete window. Beginning the second segment starts a new autocomplete window with the submodule (without the first segment). Autocompleting during the second segment will work. But if you finish out to the third segment or later, it will always duplicate the first segment you started with.

If you go back and delete the Duplicate and try again, if dot is the last remaining character, the behavior will be correct. If you delete the dot as well, it will do the module segment duplication outlined above.

The behavior seems almost right. So I'm wondering if this is an easy thing for me to work on with zero experience with the LSP or HLS

@Ailrun Ailrun added editor: vscode type: bug Something isn't right: doesn't work as intended, documentation is missing/outdated, etc.. labels Aug 21, 2020
@georgefst
Copy link
Collaborator

I'm wondering if this is an easy thing for me to work on with zero experience with the LSP or HLS

https://github.com/digital-asset/ghcide/issues/613

It's tagged "good first issue"!

@Ailrun Ailrun added component: ghcide status: blocked Not actionable, because blocked by upstream/GHC etc. and removed editor: vscode status: blocked Not actionable, because blocked by upstream/GHC etc. labels Aug 28, 2020
@wz1000 wz1000 closed this as completed Sep 17, 2020
pepeiborra pushed a commit that referenced this issue Dec 27, 2020
This has caused a bunch of issues in DAML where GHC seems to randomly
panics when completions are requested, see
digital-asset/daml#4152 for the error. I am
not entirely sure what is going wrong there but `getDocs` also goes
through the GHCi codepaths which are known to cause issues with
ghc-lib so for now, let’s disable it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: ghcide type: bug Something isn't right: doesn't work as intended, documentation is missing/outdated, etc..
Projects
None yet
Development

No branches or pull requests

4 participants