<div dir="ltr">Also, this might help with the dynamic-require approach:<div><br></div><div><a href="http://docs.racket-lang.org/tools/drracket_get_extend.html?q=drracket%3Aget/extend%3Adisallow-re-extension%21#%28def._%28%28lib._drracket%2Ftool-lib..rkt%29._drracket~3aget%2Fextend~3adisallow-re-extension%21%29%29">http://docs.racket-lang.org/tools/drracket_get_extend.html?q=drracket%3Aget/extend%3Adisallow-re-extension%21#%28def._%28%28lib._drracket%2Ftool-lib..rkt%29._drracket~3aget%2Fextend~3adisallow-re-extension%21%29%29</a><br> </div><div><br></div><div>Robby</div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Aug 31, 2013 at 2:57 PM, Stephen De Gabrielle <span dir="ltr"><<a href="mailto:stephen.degabrielle@acm.org" target="_blank">stephen.degabrielle@acm.org</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Thanks Laurent & Jens, <div><br></div><div>Much appreciated.</div><div><br></div><div>Stephen<br><div> <br></div></div></div><div class="gmail_extra"><br clear="all"><div><div dir="ltr">--<br><a href="http://www.degabrielle.name/stephen" target="_blank">Stephen De Gabrielle</a><div> <br></div></div></div><div><div class="h5"> <br><br><div class="gmail_quote">On Sat, Aug 31, 2013 at 5:09 PM, Jens Axel Søgaard <span dir="ltr"><<a href="mailto:jensaxel@soegaard.net" target="_blank">jensaxel@soegaard.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div dir="ltr">When writing code that require DrRacket to restart I usually open two DrRackets. In one instance of DrRacket I write the code - this is usually in an old version. In the other I test the code. This way I don't need to reopen the source file after each restart.<div> <br></div><div>Another tip: To make DrRacket restart faster remove all tools you don't need. DrRacket actually start very faster with no tools.</div><div> </div></div><div class="gmail_extra"><br><br><div class="gmail_quote"> <div><div> 2013/8/31 Stephen De Gabrielle <span dir="ltr"><<a href="mailto:stephen.degabrielle@acm.org" target="_blank">stephen.degabrielle@acm.org</a>></span><br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div><div> <div dir="ltr"><div><div dir="ltr"><div>Hi, </div><div><br></div><div>I'm starting to fiddle with DrRacket plugin ideas (again), and I was wondering if any tool developers can share their processes for developing tools, </div> <div><br></div><div>What I used to do was dump my tool in a collects directory and run 'raco -L toolname', followed by restarting-the-Doctor. If it failed I would remove the tool from /collects/ and restart again.</div> <div><br></div><div>This is a bit frustrating as it can be quite time consuming, and I disable as many tools as possible to make restarts quicker.</div><div><br></div><div>Is there a better way to develop plugins?</div> <div><br></div><div>Cheers, </div><span><font color="#888888"><div><br></div><div>Stephen</div></font></span></div></div> </div> <br></div></div>____________________<br> Racket Users list:<br> <a href="http://lists.racket-lang.org/users" target="_blank">http://lists.racket-lang.org/users</a><br> <br></blockquote></div><span><font color="#888888"><br><br clear="all"><div><br></div>-- <br>-- <br>Jens Axel Søgaard<br><br> </font></span></div> </blockquote></div><br></div></div></div> <br>____________________<br> Racket Users list:<br> <a href="http://lists.racket-lang.org/users" target="_blank">http://lists.racket-lang.org/users</a><br> <br></blockquote></div><br></div>