2010/9/21 Laurent PETIT <laurent.pe...@gmail.com> > 2010/9/21 Phil Hagelberg <p...@hagelb.org> > > On Mon, Sep 20, 2010 at 10:07 PM, Kevin Downey <redc...@gmail.com> wrote: >> > On Mon, Sep 20, 2010 at 7:33 PM, Robert McIntyre <r...@mit.edu> wrote: >> >> If it is to be deprecated, is there a "correct" way of achieving the >> >> same result (having things automatically loaded when you create the >> >> repl?) >> > >> > user.clj is very useful, I'd rather keep it. >> >> Agreed; there are some neat tricks that would be really hard to do without >> it. >> > > > Which ones ? It's a true question, 'cause I never used it, so maybe I'm > missing something interesting. > > Anyway, if it provides interesting features, would it be possible to find a > "better" way of providing the same level of features, with the same level of > simplicity, but in a more "robust" way when facing the case of a project > using several libs which may or may not have left some user.clj in their > default package ? >
Trying to answer my own question (brainstorming mode): * making the user.clj contextual to a project / artifact: should work well with repls started from maven, cake, cljr, lein, gradle, etc. : <artifactId>/user.clj (e.g. net.cgrand.parsley/user.clj, paredit/user.clj) ? -- 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
