2010/7/20 Rick Moynihan <rick.moyni...@gmail.com> > On 19 July 2010 22:25, Laurent PETIT <laurent.pe...@gmail.com> wrote: > > > > 2010/7/19 Peter Schuller <peter.schul...@infidyne.com> > >> I also sympathize and agree that it can be hugely problematic if an > >> environment stomps on your carefully prepared REPL in ways you don't > >> expect. I'm not sure how to best reconcile these two concerns. > > > > Yes, that's currently the most important point I'd missed so far. So I > think > > IDEs may not simply have to provide "white/black" behaviour concerning > > dynamic feature, but also a middle path (though I guess by reading the > > comments that I may still make the default behaviour be "automatically > > reload", and for people wanting the maximum safety, "don't automatically > > reload"). > > The middle way, seems like a nice option. How about, having save as > just save, providing a save-all-and-reload-all option; and using > editor overlays to indicate un-evaluated sexpressions (that haven't > yet been sent to the repl). In light of this, you might also be able > to show vars that exist in the current repl environment, that don't > yet exist in a file (though this is arguably more complex). >
Yes, I'm starting to thing about this as the final target. Not surprisingly, it's not the easiest one to reach :-) > > Just my 2 pence worth; but I agree with others that save should be > just save, and evaluate should be separate... I come from the > SLIME/Emacs camp, and yes desynchronisation is sometimes a problem, > but its pretty easy to clean the environment and evaluate everything > again. > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
