erlang / erlide_kernel Goto Github PK

It would be much easier to export with a script than manually, making sure that versions are updated and beams are put in the right places.

It's possible that the plugins will have to follow the apps closely (see #1)

Implement as real OTP apps.

Some "initialize" function is still needed, so that the configuration from the (Eclipse) client can be sent.

In the sourcer project, a submission has updated and improved the indentation code to match the emacs style and also properly handling multiline strings. This will become available via the language server, but until that is available, maybe updating the erlide code would be agood idea?

https://github.com/Microsoft/language-server-protocol

It looks like more and more tools start to use this, no need to reinvent the wheel.

Currently, erlide parses the code as AST and traverses that whenever it needs information. It would be more efficient if a flat database of symbols can be built and searched, something like ctags but with more details.

This would be useful even for non-LSP erlide.

I seem to have trouble debugging code with map literals in the source ie #{id => Root}. When I attach the debugger I am able to hit breakpoints but when I come to a source line with a map literal in it I receive an exception of

{'NYI',{map,17,
    [{map_field_assoc,18,{value,18,id},{var,18,'Root'}}
...

This might be the offending line (with the note about brutal kill unrecognizable expressions).

• Eclipse Neon 2
• Erlang 18.3
• Linux

Some OTP apps (inets, diameter, snmp, wx) have a non-standard structure and the source code isn't found by erlide.

We can't search 'src' recursively because users have projects where the subdirectories should be ignored.

Probably the fastest solution is to add special cases for these apps.

Same as erlang/erlide_eclipse#312

it may be unnecessary while engine is in-process, but is a must for external servers.

Many tests from erlide can be moved here, making it easier to find out that something has broken.

Two simple modules are attached: f3 and f3lib. Change the filenames to f3.erl and f3lib.erl, and add them to an Erlang project. View the f3 module in Eclipse with Erlide. Place the cursor after the colon in line 8. Press F3, or menu-click and do "Open Declaration". This should cause the f3lib:b/4 function to come into focus. However, it is the f3lib:b/3 function that gets the focus.

at the moment, I think only the builders need to be separated

We don't want to have to release everything as soon as something small changes.

same as for erlide_eclipse