@tony.kay: Only a fairly ghetto solution for this right now sorry, see https://github.com/cursiveclojure/cursive/issues/38#issuecomment-26373091 and https://github.com/cursiveclojure/cursive/issues/708#issuecomment-83769578

I’m planning a better semi-automatic solution for this soon.

@cfleming: Ah, ok, thanks! Ghetto is better than nothing

Anyone a idea what is here the problem :

@roelof slurp is looking either in src/core_functions (alongside core.clj) or resources/, and the file lives in neither place

Either change filename to an absolute path, or a correct relative path

oke

I moved it into resources but the same error message

Try a relative path

(slurp “../../../resources/suspects.csv)

Or just put the absolute path, since I’m sure this isn’t a production application 😄

Hi guys. I noticed that with the latest Cursive version, REPL takes an order of magnitude longer to start. It says it’s calculating classpath. Subjectively, the REPL start used to be way faster before for the same project. Has anyone else noticed that?

the relative path does not work

also the absolute path : (slurp "c://Users/rwobb/IdeaProjects/resources/suspects.csv")

@roelof That’s not the absolute path. It doesn’t have the project directory in it. You’re getting a FileNotFoundException, so the file isn’t where you’re telling slurp to look

oke, I will change it

thanks, changed it to (slurp "c://Users/rwobb/IdeaProjects/core_functions/resources/suspects.csv") worked

BTW it’s been brought to my attention that the use of the word “ghetto” to imply something that’s not of good quality can sound pretty offensive, in particular in the US. My apologies, it doesn’t have the same connotation where I’m from and I certainly didn’t intend anything like that.

@dmi3y: A few people have commented that it seems to take longer to start, but I’ve timed it at least on my machine and the time is generally the same. It’s actually calling the same code (in a slightly different way, admittedly), so I don’t think there should be a big difference.

@dmi3y: But if you’re literally seeing an order of magnitude difference then that sounds like a bug.

What I think usually happens is that your attention is drawn to it by the progress bar, and additionally that now happens before the REPL window is opened, which makes it feel longer till anything happens.

It could be, yes

@cfleming: I’ll time it against a previous version of Cursive on which I think it was faster.

@dmi3y: Thanks. I’d be very interested to know your results.

I’m actually considering a change which would cache the REPL classpath in case nothing has changed, but that can only be done when there are no snapshots involved.

That would make subsequent startups very fast, though.

Sounds cool!