atom-elixir Problem with the default atom autocomplete behaviour

It doesn't autocomplete with variables on the module, functions on the same module or with previous used words in the files like it's the common atom behaviour

May 11 '16 20:05 mrkaspa

@mrkaspa Autocomplete for used words in the file is not supported yet. Variables on module, functions on the same module should all work as long as the module has been successfully compiled. There's a new version v0.2.1. You might try it and see if the problem is gone. Let me know if it's not.

Jun 27 '16 20:06 msaraiva

I also have a problem with autocomplete. you_complete_me stops working after enabling atom-elixir plugin. Don't know how that should be implemented, but it seems to be possible to make them work together. If I'm not missing typescript plugin worked well with ycm.

YCM also has a feature to suggest all the words in opened files.

Jul 06 '16 14:07 styx

@msaraiva yeah this has to be posible and it's pretty useful, I've got the lastest version but doesn't work yet

Jul 08 '16 12:07 mrkaspa

I guess this would solve the issue. I'll try to implement this before the next release. PRs are welcome.

Thanks for reporting!

Jul 08 '16 13:07 msaraiva

@msaraiva you were right https://github.com/msaraiva/atom-elixir/pull/37

Jul 08 '16 13:07 mrkaspa

@mrkaspa yeah, but we need to have that value based on a preference so the user can choose the preferable behaviour.

Jul 08 '16 14:07 msaraiva

I guess we all waiting for #36

Oct 01 '16 12:10 rubencaro