Re: [jdee-devel] Proposed New Structure (starter for 10)
Brought to you by:
paullandes
From: <phi...@ru...> - 2015-10-28 09:57:35
|
Troy Daniels <uda...@gm...> writes: > On Tue, Oct 27, 2015 at 6:38 AM, Phillip Lord <phi...@ru...> > wrote: > >> >> That's straight-forward, since the JVM knows about the classpath. >> In fact, it should work already. I *think* calling >> >> (cider-classpath) >> > > That was pretty simple. I had already found that, and just needed to be > sure that functions called by the user would call the method that was > calling cider. > > That is working, at least for imports. I just created an import in a file > that did not have a prj.el. The first import was pretty slow, since it > started the nrepl *and* the beanshell, but it is connected. In this multi-core day and age, we could always have a "start-automatically" option. >> should do this for the current-buffer. >> >> If I remember correctly, the stacktrace handling from cider works as >> well. At least, those are the two bits of middleware that I have added >> direct from cider. >> >> > Is there other middleware that is likely to be useful? Yeah, possibly. The inspector (a class browser) might work. wrap-out captures standard out. And wrap-apropos might be useful also. And even complete might work somewhat. The devil, unfortuanately, is in the detail though. Even the stacktracer is imperfect, because it has "hide clojure.*" classes as a GUI element which is unlikely to be useful. Still Bolzhidar is a nice chap, and I am sure would help separate or optionalise functionality if we needed it. Phil |