On Mon, Jan 6, 2014 at 11:10 PM, Colin Fleming <colin.mailingl...@gmail.com>wrote:
> Since Cursive (http://cursiveclojure.com) resolves everything statically > from source, ClojureScript completion and navigation works for most > symbols. There are still a lot that it doesn't know about since > cljs-specific functionality is still pretty low, so js/* symbols have no > support, and any functions included from Closure are not found either. But > for pure cljs it should work pretty well. There are quite a few people > using Cursive for cljs dev now, despite the slightly embarrassing lack of > explicit support :-) > Hi Colin, I just installed Cursive and looks very promising. I'll try using it. Do you plan to explicitly support ClojureScript? Do you have an ETA? That would be awesome, because viewing the implementation of Clojure's core libs is very valuable and from what I understand, there are differences between Clojure and ClojureScript (e.g. protocols are at the bottom in ClojureScript) and it would be valuable if I could click on a function and see its ClojureScript specific code and documentation. Also handling the Javascript interop would be awesome too. Thanks, -- Alexandru Nedelcu www.bionicspirit.com PGP Public Key: https://bionicspirit.com/key.aexpk -- -- 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 --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
