-
-
Notifications
You must be signed in to change notification settings - Fork 227
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
Eval current form (when require
call) causes REPL window to switch to user ns
#302
Comments
Update: This is more of an issue than I thought. I made sure to do a fresh install of Calva to make sure I didn't have any custom changes installed (removed the old extension folder in ~./vscode/extensions). I realized any time the "eval current form" command is run, the namespace in the REPL window switches back to user. Updated steps to reproduce:
Image demo; That Update 2: I tried to debug this. I stepped through the execution of the |
Sounds bad. I'll have a look at it today. |
OK. This will take a little while to figure out. It is hard to diff because the changes are in different repositories. But I will probably solve this together with another issue regarding namespace behaviour in the REPL window. No ETA, yet, but nag me on Friday if no updates here by then. 😄 |
This used to not occur on master as of 2.0.33, but it does now. I know because I do this sequence often in my daily work.
Here are the repro steps:
ctrl+alt+c, ctrl+alt+n
)ctrl+alt+c, e
on something like(require '[hello.world.test-req :as tr])
user
namespace. If you try to eval something from the namespace of the prompt, it will say undefined because you're REPL is actually in theuser
namespace.This is different from the issue where trying to resolve an undefined var switches the namespace, because it switched namespace on the require statement sent from the editor window. Also, there are no errors in the namespace being required (just to clarify).
The text was updated successfully, but these errors were encountered: