<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>I have a slightly modified version of sync that attempts to work around this issue, you can find it here: <a href="https://github.com/sbalea/sync.git">https://github.com/sbalea/sync.git</a></div><div>It's not bulletproof, which is why I haven't yet submitted a PR for it, but it seems to work in the majority of my use cases.</div><div><br></div><div>Mihai</div><div><br></div><div><div>On Jun 2, 2013, at 5:15 AM, Felix Gallo <<a href="mailto:felixgallo@gmail.com">felixgallo@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">I'm developing a medium-sized erlang node comprised of several interacting applications. In doing so, I'm finding myself staring at the output of <div><br></div><div style="">./rebar compile && ./rebar generate && ./rel/bin/mynode/bin/mynode console</div>
<div style=""><br></div><div style="">quite a bit more than is perhaps wanted.</div><div style=""><br></div><div style="">I thought that <a href="https://github.com/rustyio/sync">https://github.com/rustyio/sync</a> might be the answer to all of my problems, as it advertises hot code reloading on file changes. However, I haven't yet coaxed it into working inside the ./rel/bin/mynode/bin/mynode console environment; I suspect it's detecting the code changes, and recompiling the code, but it's not redeploying into the release, so doesn't reload the beams.</div>
<div style=""><br></div><div style="">So then I thought that maybe it's dumb to include the reltool build in the development cycle, maybe the pro erlang way is to just run erl by hand like our forefathers did before us. But when I give that a shot, as an OTP neophyte, I have this lurking feeling that I am aiming a gun at my foot.</div>
<div style=""><br></div><div style="">For those of us who don't believe in emacs, what's the one true optimal way to tighten up the development loop here?</div><div style=""><br></div><div style="">F.</div></div>
_______________________________________________<br>erlang-questions mailing list<br><a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>http://erlang.org/mailman/listinfo/erlang-questions<br></blockquote></div><br></body></html>