Closed MarkoMin closed 8 months ago
Hi @MarkoMin!
I've had this issue with earlier versions but with 0.50.0/master I can not reproduce it.
I am using nvim v0.9.4 with this set of plugins. Completion provider is nvim-cmp. Maybe this is coc related?
cheers!
This can happen if parsing of the -export expression fails. I got an idea how to make it more robust.
I've merged a fix for this now. Hopefully it will resolve the issue :)
Works as a charm, great job!
@plux I just noticed the same thing for -export_type
. Maybe we should go with function like "is_in_something_that_accepts_FAs" (import, export, export_type, import_type might come soon, etc.
EDIT: my bad, I was on previous version......
Describe the bug How can I complete functions to
f/A
instead off(Args...)
when trying to export them? When I want to export few functions in export, the first function is correctly expanded tof/A
(if I autocompleted-export
), but next ones get wrongly completed tof(Args...)
. If I don't autocomplete, not even first one works correctly.To Reproduce Define a module with 2 functions:
really_long_name/3
andreally_really_long_name/3
. Then type "-exp" and autocomplete it to-export([|]).
(| is cursor mark :D). Now type "really_lo" and hit autocomplete, you'll get "really_long_name/3". Then type ", really_rea" and autocomplete it, you'll get-export([really_long_name/3, really_really_long_name(Arg1, Arg2, Arg3)]).
- which is wrong I believe. Tested on 0.48.0 and 0.50.0 innvim
withcoc
as lsp plugin, OTP26. If I remember correctly this thing worked on VS-code, but I'm not 100%.