Skip to content
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

REPL automatically switches back to user namespace #212

Closed
svdo opened this issue Jun 8, 2019 · 4 comments
Closed

REPL automatically switches back to user namespace #212

svdo opened this issue Jun 8, 2019 · 4 comments

Comments

@svdo
Copy link
Contributor

svdo commented Jun 8, 2019

Hi,

First thanks PEZ for Calva! I'm new to Clojure and chose to use VSCode and Calva and was very happy. Now with v2 I'm even happier, very well done.

I have a strange "phenomenon": I'd like to use the setting "Sync REPL namespace to current file" but it causes strange behaviour. I have a Leiningen project (created with lein new app, nothing special about it). I then use jack-in to start a REPL. I have the source code and the REPL side-by-side. Now when I'm in the source code, I see the REPL namespace switch to that of the source code file, as expected. So far so good. Now when I click in the REPL window to try some things directly from the REPL, immediately on clicking in the REPL window its namespace changes back to user. Click source file, changes to my namespace, click REPL, changes back to user.

I'm assuming this is a bug, but if I'm doing something wrong please don't worry about hurting my feelings ;)

@svdo
Copy link
Contributor Author

svdo commented Jun 8, 2019

I made a video of the behaviour and noticed that the behaviour I'm describing is not 100% consistent. The video visualises the mouse clicks so that you can better see what I mean. I'll drop the video in Slack #calvadev if you don't mind, not sure where to put it otherwise (I don't want to create an account on any of the video-sharing web sites). https://clojurians.slack.com/archives/CBE668G4R/p1559980249249100

@PEZ
Copy link
Collaborator

PEZ commented Jun 8, 2019

Thanks! I think I know what's going on. It's not you!

PEZ added a commit that referenced this issue Jun 8, 2019
PEZ added a commit that referenced this issue Jun 8, 2019
@PEZ
Copy link
Collaborator

PEZ commented Jun 8, 2019

Thanks for reporting this! Version 2.0.5, just released, should fix this. Please close this issue if that checks out for you.

@svdo
Copy link
Contributor Author

svdo commented Jun 8, 2019

Superb, it works. 👏

@svdo svdo closed this as completed Jun 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants