Hello Mark,
2013/4/24 Mark Engelberg <
mark.en...@gmail.com>:
> A while back, we discussed :injections. At the time, I was mourning the
> change away from having clojure.repl always present in the REPL. It gets
> tedious to always have to type (use 'clojure.repl) before using doc or pst.
> Putting :injections in the project.clj was the closest thing, but only
> worked to include the clojure.repl vars in the first namespace you start up.
Yes, AFAICT that's still a restriction in Leiningen 2: the REPL server
does not honor :injections (yet?)
> I notice that in the most recent version, :injections doesn't seem to work
> at all. I find this curious since the new version seems to generally have
> better support for leiningen project settings.
>
> What is the current state of things regarding injections, and is there an
> alternative way to get clojure.repl vars available in the REPL?
I'd say I would not expect :injections to work with the stable 0.12.3
version, since it does not honor at all what is in project.clj (but
the :dependencies stuff).
I can see it working with the 0.13 beta version, as expected (with the
restriction that it's indeed only working for the first namespace used
when leiningen starts up).
>
> Thanks,
>
> Mark
>
>
> On Tuesday, November 20, 2012 2:08:43 PM UTC-8, Chas Emerick wrote:
>>
>> On Nov 18, 2012, at 8:52 PM, Mark Engelberg wrote:
>>
>>> That said, there is something to be said for one's REPL referring certain
>>> vars into *ns* on every in-ns (I particularly miss having pp available
>>> everywhere,
>>
>>
>> Isn't that what the :injections key in project.clj is supposed to do?
>>
>>
>> No; forms added there are evaluated when the REPL starts, but at no other
>> time.
>>
>> - Chas
>
> --
> You received this message because you are subscribed to the Google Groups
> "counterclockwise-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
clojuredev-use...@googlegroups.com.
> Visit this group at
http://groups.google.com/group/clojuredev-users?hl=en.
> For more options, visit
https://groups.google.com/groups/opt_out.
>
>