Create jump-to-resource function

[technomancy]

The idea here is that if you have a resource being loaded off the classpath (say by clojure.java.io/resource, but it could also be by something like enlive's deftemplate) that you should be able to jump to it with a single keystroke.

It's possible that the existing M-. functionality could be enhanced to do this as long as there's no ambiguity. Perhaps if M-. is invoked when the point is on a string, it could be interpreted as a classpath lookup? We'd also want it to work on namespaces I think, which would be on symbols, but maybe that's separate.

[gtrak]

I like this idea, I've already written some code to try and determine if a string's a file path or a classpath resource for the 'info' op. This is used to provide file-and-line information either within jars or on the FS.

https://github.com/gtrak/cider-nrepl/blob/master/src/cider/nrepl/middleware/info.clj#L48

I could pull it out into an nrepl op, what do you think a good name would be?

My vote's on 'resource'.

I'm not sure how to retrofit the elisp to handle this case, but I'll be thinking about it. M-. seems natural.

[bbatsov]

Yeah, a resource op sounds like a good idea to me.

[bbatsov]

@jeffvalk What are your thoughts about this?

[jeffvalk]

I like the idea. Regarding cider-jump, though, I wouldn't want to see resource behavior preferred to info within strings -- I find it really handy to be able to jump to var/class names in docstrings and comments. Perhaps cider-jump could try info first and then resource?

[bbatsov]

Yeah, I think we should have separate functions. Perhaps we should rename cider-jump to cider-jump-to-definition or something else more descriptive and the other command would be cider-jump-to-resource. Btw, do we need anything more than io/resource to make a resource middleware?

[jeffvalk]

Nope, calling io/resource would essentially be the entire op handler.