> Why does refactor do it differently?

@dominicm It’s basically part of the overall approach of cljr - most of the functionality there depends on parsing the entire project code on operating on the resulting AST. swank-clojure and CIDER generally rely on just analyzing the state of the running application.

Meaning we never build an AST and just inspect whatever we can from interactions with the nREPL server. For find and replace the problem with this approach is that obviously this works only for loaded namespaces, but you can easily load all namespaces if you want to do this.

Building the AST up front is pretty slow for big projects and you obviously have to keep rebuilding it all the time.

The old SLIME approach worked pretty well even though it was pretty primitive. I was just about to port (and enhance it a bit), when my CIDER time dropped to close to 0.

I've taken two weeks off work. I'm mostly playing VR, but I might have a go at seeing how that works out.

I haven’t played anything in while, so I’m not sure what’s VR is. 😄 I doubt it’s Virtual Reality. 🙂

@ghsgd2 should have been more specific

type , in your cider repl

you get a list of commands to choose from

pick refresh

@benedek

1. Caused by clojure.lang.Compiler$CompilerException

seems to be a compilation error

anagram_test line 7 col 10

@benedek Thank you! Yeah, this time it was a compilation error (I've done a refactoring and then undo'ed it but undo reverted to previous state only one of files). Sorry for that.

nw