Fork me on GitHub

@cfleming: are there any features planned where you would be able to tell Cursive that a certain form - creates vars in some context - is a custom threading macro


@cfleming Might have found an issue, but I assume there's probably an existing issue I couldn't find - I had a file with an unclosed namespace declaration (unmatched opening paren, i.e. no closing paren). Tried to open the file and got a stackoverflow error every time, even after multiple restarts. I messed around and traced it to a deftype statement. Seems like it happens even when the file is open as long as there are 2 or more protocols on the deftype. With one, it doesn't seem to happen. I closed the parens by opening the file in another editor and fixing the mistake, and all is well again. I'm guessing Cursive is causing this since it only happens when the plugin is active and I am assuming you do some parsing when loading the file. I'm on Intellij15, OSX. I've only seen this happen with a namespace, not with unclosed functions or other s-expressions.


I'm really struggling to get a figwheel repl running in cursive using a luminus template as the starting point. I followed the steps here: but the figwheel server doesn't see the built clojurescript (which luminus comes configured to put in target/cljsbuild), presumably because figwheel doesn't do leiningen profile merging, so it is ignoring all the luminus project.clj settings and just using the default resources/public directory. Anyone else have any luck getting this working?


I haven’t tried it myself, but I’m planning to soon to document this since it’s a struggle for a lot of people I think. I don’t use CLJS myself so I’m still not sure of all the required possible configs.


I’m planning to make a built-in CLJS REPL type which will hopefully do all this automatically.


@imre: Yes, both of those are planned. The full solution is an API that people will be able to use to add support for macro forms with a public repo which everyone can contribute to.


@imre: I’m planning a workaround until I get that done, which will allow simply saying: this form defines a var like def, this is a binding form like let, or this is a threading form like ->.


That’ll probably be an 80% solution.