-
-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nREPL: namespace not found #149
Comments
Can you create a temp repo (a gist would probably work) I can try on? |
https://github.com/oskarkv/nonamespace |
Actually given that I would expect a plain old |
Had to repeat the dance a couple of times before I saw the error in question. A A potential workflow improvement would be to replace our "require on first eval" logic with "require on |
I should add that this replacement logic needs to work for ClojureScript too. So the first step would be checking if a missing namespace triggers |
I think the fix for #161 should render this moot as well. |
I'm not 100% this is an issue with fireplace, but here goes.
I have:
lein version 2.3.4
fireplace "Use info op for :Doc" 020a10d
tools.namespace 0.2.4
To reproduce the issue:
I have 3 files:
user.clj:
nonamespace/a.clj:
nonamespace/b.clj
Now run
(clojure.tools.namespace.repl/refresh)
It should say:Now, change
nonamespace/b.clj
to introduce an error. For example, remove the paren beforedefn
. Run:Eval (clojure.tools.namespace.repl/refresh)
in vim. It should say:Note that the above step is necessary to reproduce the issue!
Now go to
nonamespace/a.clj
and save/write it, just to make tools.namespace reload it.Run
:Eval (clojure.tools.namespace.repl/refresh)
in vim. Vim says:nREPL: namespace not found
But, running
(clojure.tools.namespace.repl/refresh)
in the repl outside vim works as expected, i.e. the result is:If I fix the error, i.e. replace the missing paren, and run
(clojure.tools.namespace.repl/refresh)
vim will keep sayingnREPL: namespace not found
. Restarting the repl gets rid of the problem.The text was updated successfully, but these errors were encountered: