Closed AeroNotix closed 3 years ago
Nope, that should be ok, but OTP itself doesn't guarantee binary compatibility between releases that are more than one major apart so I'd recommend not going further than that because it may screw with the communication between the nodes.
EDTS itself should preferably also be compiled with the version of erlang that you will run it with inside emacs.
Right because I have several projects on the go that use versions between R16* and R19. Remind me, can I have EDTS start up separate EDTS versions based on the EDTS per project configuration file?
Not out of the box I'm afraid. You customize the command (and thus the version) that is used to start the EDTS node based on the project you're in but EDTS will always assume the node is called edts so you can't run more than one at a time.
Hm, then I'll keep hacking on EDTS and see what I can come up with.
On Fri, 7 Apr 2017 at 16:38 Thomas Järvstrand notifications@github.com wrote:
Not out of the box I'm afraid. You customize the command (and thus the version) that is used to start the EDTS node based on the project you're in but EDTS will always assume the node is called edts so you can't run more than one at a time.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/tjarvstrand/edts/issues/228#issuecomment-292554457, or mute the thread https://github.com/notifications/unsubscribe-auth/AA7kWu7rZHL5OKL0cRfL0SZq7HCvrFx3ks5rtkpJgaJpZM4M2zgl .
@AeroNotix: Did you solve it? I guess you want something similar to #188
I'm debugging an issue where EDTS returns that modules don't exist, I know they do (they're mnesia, for example) and in the debug EDTS buffer it complains about beam chunks being invalid. My EDTS node's version is different from the project's version. Do they need to be exactly the same?