@ag, @malabarba - just wanted to ask about the same problem, and saw your messages. I've just updated CIDER to 20160725.136, and bumped up Emacs, and got exactly the same problem. Emacs 25.1.50.5, latest from master, commit 682fdae. The previous version of Emacs was older by just a few weeks, about 130-140 commits, and it was fine. Maybe it will help you to narrow it down.

@malabarba: just checked out Emacs 25 from 4 weeks back, a randomly chosen commit 0644e6f - CIDER is fine. So there you have it - something got broken between 0644e6f and 682fdae. Hope it helps. Let me know if you need any additional info or help in recreating it. Cheers!

Is anyone developing in a docker container using emacs and cider? If so, are you able to jump to fn definitions in a different ns? I keep getting no source locations and https://github.com/clojure-emacs/cider/issues/589 doesnt' seem to address it for me

@petr: I'm using docker-compose and I get around this by mounting my home directories, source, and .m2 so paths line up.

It feels like overkill to relativize eg resource paths, if cider goes down that route.

it might be nice to expose some vars or regexes for this just on the client code

but you will want to mount your source dirs inside the container to enable things like tools.namespace to watch files

@gtrak: That is kinda nasty, but I'll take it if it allows me to jump to the location

Somthing like this? volumes: - "~/.m2/.:/.m2"

yea but no tilde on the right side

not sure about the expansion rules but this has been working for me:

- ~/dev/mycode:/home/gary/dev/mycode
      - ~/.m2:/home/gary/.m2
      - ~/.boot:/home/gary/.boot

That's really interesting

the absolute paths are what need to line up

That's fair

also have to tell it to use /home/gary/.m2

That also means I have to run lein deps on the host machien

environment:
      BOOT_LOCAL_REPO: /home/gary/.m2/repository
      BOOT_HOME: /home/gary/.boot

so, you don't have to run lein deps on the host

additionally, I run it as my user 🙂

hacks upon hacks

I see that

I appreciate the help:)

happens to be 1000:

user: 1000:1000

otherwise when docker writes files it'll be as root, and that can cause problems later

Where did you set that?

I.e. the user

in docker-compose.yml service block per service

I meant more that I didn't know you could set the user like that

1000 comes from your host

so if I cat /etc/group, there is a line:

gary:x:1000:

Damn, that's great! Thank you! I'm going to give this a try

'id -u' also gives it to you

good luck!

err, is anyone else's cider trying to inject to "0.14.0-SNAPSHOT"?

ooh, this seems to be because I haven't pinned a particular version.