big big appreciation for the simple change in the repl to quickly include the repl utilities. Hitting , in the repl brings up that handy menu and require-repl-utils is outstanding!

big ups for such a small simple change

didnt’ know about this! cool!!!

Someone should do a quick and dirty Cider Emacs/spacemacs video on how they develop with clojure. I’m always worried im missing helpful features because i dont know what i dont have 🙂 Of course, there are probably 10 of them out there i haven’t watched…

@drewverlee @magnars zombie themed game development is exactly that http://www.parens-of-the-dead.com

probably not the most up to date but still an eye opener

@drewverlee https://www.youtube.com/watch?v=aYA4AAjLfT0

Not sure if you’ve seen this one, but it covers a lot of ground.

@bozhidar I just tested the xref.clj code, it works verbatim fwiw. But I don't really see the value given that it works on a symbol not a var for cross-referencing.

I got different sets of results for clojure.core/map and map, for example.

I guess I'm questioning the purpose of the code, before I go any further.

@dominicm I’m not saying there’s not room for improvement there. 🙂 Ideally potential matches should be resolved to make sure they are really the var you’re looking for, but that’s relatively easy to do.

I think this would solve the problem you’ve observed.

It does, although input becomes harder for clients.

Not sure that's a problem though

Falls over for shadowing of course 😕

can anyone try cider-browse-ns ? i'm not sure its working right now

e.g. #'clojure.core/ns is shadowed in #'clojure.core/keyword with it's ns parameter.

@dpsutton It works for me. What problem are you experiencing?

Not an nREPL dict

> It does, although input becomes harder for clients. Isn’t the input always a var? Not sure how it becomes harder for clients.

(cider-sync-request:ns-vars-with-meta namespace) is coming back nil

I don’t recall any changes recent changes there.

i'll check it tonight. just wondering if it was me or in general. i think someone did some work on the nrepl side recently, but also i may not have restarted emacs since pulling

oh i thought the resources listing stuff was changed

but i didn't follow along closely. might be unrelated

@dominicm worked on some things, but nothing related.

ok. i'll dig later. thanks for confirming it is working

> e.g. #'clojure.core/ns is shadowed in #'clojure.core/keyword with it’s ns parameter.

Yeah, that’s true, but few things are ideal and I’m happy to settle for something that’s useful. 🙂

To deal properly with locals we need to parse the code and even then, there would be some potential for mistakes.

At that point, we're building what refactor-nrepl does already 😄

Why is it that you want this over what refactor-nrepl offers?

Because building the AST for the project is ridiculously slow and you have to keep rebuilding it after changes for each file.

How slow is ridiculously slow?

Depends on how big the project is. It was slow enough to decide I don’t want anything related to parsing code in CIDER itself.

Don’t recall the exact details.

And I seem to recall there were a ton of bugs related to the parser, at least in the early days.

I’ve always liked the simplicity of relying on just the application state - felt very Lispy to me.

It just occurred to me that I do recall seeing a 2 minute AST on a project in the past. We've not reached that scale on my current project yet though.

The xref code would need some tweaking to integrate the locations where the match was found

And maybe a bit of general cleanup. 😄 I seem to recall it was written in the era of Clojure 1.2 or something like this.

yeah, it didn't read idiomatic at all