dm1try / ilexir Goto Github PK

+----------------------------+
|                            |
|                            |
|                            |
|                            |
|                            |
|                            |
|                            |
+---------------+------------+
| iex(1)>...    | warn: tada |
|               |            |
+---------------+------------+
+----------------------------+
|                            |
|   +---------------+        |
|                            |
|                            |
|                            |
|                            |
|                            |
+---------------+------------+
|~ git status   | %{eval:    |
|               |   "result"}|
+---------------+------------+

Beside standard interactions(hide/show), client code should be able to "stick" a buffer into a specific position, create and reuse it depend on current context(a running host app/a performed action).

• ESpec runner
• ExUnit runner
• doctest support

The current workaround is "warm-up" step in travis config :(

example: :erlang.decode_packet

this - https://github.com/dm1try/ilexir/tree/master/rplugin/elixir/apps/ilexir/hosted/ilexir + host apps manager

This will allow using the core "inspection" interface from different editors.

closed via a2afe32

on lookup

Should allow add errors/warnings to the nvim quicklist and highlight them simultaneously.
It makes sense allow to group the errors that are delivered from different sources.

Add ability to resolve issues added by linters automatically

They should be cleared if a buffer is changed.

precompiled Elixir which is installed using asdf packet manager has Jose home path in debug info:

/Users/jose/OSS/elixir/lib/elixir/lib/keyword.ex
/net/isildur/ldisk/daily_build/19_prebuild_opu_o.2016-12-12_21/otp_src_19/lib/kernel/src/gen_tcp.erl

Solution: allow to provide paths to a local source(how will it work for different Elixir/OTP versions?)
The workaround: use a revision ref for installing through asdf to force the local compilation.

When we switch the context to "non-elixir" buffers any command that does not include explicit app id should be applied for last used application.

"single-file-at-once" compiler, the core component of "compile-first" approach.

it should be able to cache a compiled file environment(__ENV__)/other_useful_data retrieved on the latest compilation and return it by request. Such data will be used by different components in the future(code completion/inline evaluation/go to def/etc)

User should be able to compile plugin with disabling some features at all.
Also he should be able change some behavior(running linters/compile on save/etc) using standard way through vim config.

For example, ignore "protocol has been already consolidated".

For example function get_and_update_in/3 and macro get_and_update/2 from Kernel.
Only the macro appears.