Speaking of autocomplete. I noticed recently that when modules are aliased they don't autocomplete in releases. It works correctly in regular iex.
> On 28 Nov 2016, at 08:40, José Valim <
jose....@plataformatec.com.br> wrote:
>
> Yes, please go ahead. :D
>
> Keep in mind today the autocomplete does not have information about the evaluator (which is the process that effectively has variable bindings). However, you can reach the evaluator from the autocomplete code as follows:
>
> {:dictionary, keys} = Process.info(IEx.Server.local, :dictionary)
> keys[:evaluator]
>
> You may need to extend the evaluator process (defined in IEx.Evaluator) to respond to new messages which you will send from the autocomplete.
>
> I assume that as soon as we allow the autocomplete to access information in the evaluator, we can support both:
>
> map.f<Tab>
> some_module.f<Tab>
>
> Please let me know if you have any questions!
>
> José Valim
>
www.plataformatec.com.br
> Skype: jv.ptec
> Founder and Director of R&D
>
> On Mon, Nov 28, 2016 at 1:29 AM, Myron Marston <
myron....@gmail.com> wrote:
> IEx autocompletion is really nice, but I think there are some features missing to really make it shine. In particular, I wish it supported autocompletion of struct fields (or really, atom keys in any map). For example, in a case like:
>
> ```
> iex> map = %{foo: 23, bar: 14}
> iex> map.f<TAB>
> ```
>
> ...I'd like it to autocomplete `f` to `foo`. And if multiple fields match, it would ideally list all matches, just like how `Module.f`<TAB>` prints all the functions starting with `f` in `Module`.
>
> Depending on the complexity of implementing this, I'd be interested in taking a stab, provided the core team was in favor of this new feature.
>
> Thoughts?
> Myron
>
> --
> You received this message because you are subscribed to the Google Groups "elixir-lang-core" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
> To unsubscribe from this group and stop receiving emails from it, send an email to