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

[Windows] The ClojureScript Quick Start REPL Experiences are broken #2325

Closed
AlbertSnows opened this issue Oct 11, 2023 · 2 comments
Closed
Labels

Comments

@AlbertSnows
Copy link
Contributor

AlbertSnows commented Oct 11, 2023

Hello! This is the follow up issue to our investigation in the Clojure slack. I will also make a PR with a proposed fix to resolve this issue after.

Problem

On Windows, running the "Quick Start ClojureScript" commands for either Node and Browser does not work.

Expectation

When running a quick start command, Calva should boot up its own environment to immediately allow the user to start using some of Calva's neat features in a core .cljs file.

Outcome

When running the command, nothing happens. There's no feedback. Not in the output window, the terminals, or any popups. Some sort of behavior is happening in the background, and isn't being reflected to the user.

@AlbertSnows AlbertSnows changed the title java join semantics causes file creation issues when running the quick start command javascript join semantics causes file creation issues when running the quick start command Oct 11, 2023
@AlbertSnows AlbertSnows changed the title javascript join semantics causes file creation issues when running the quick start command javascript file path join semantics causes file creation issues when running the quick start command Oct 11, 2023
@AlbertSnows
Copy link
Contributor Author

AlbertSnows commented Oct 11, 2023

todo: move analysis to PR when made

@PEZ PEZ changed the title javascript file path join semantics causes file creation issues when running the quick start command [Windows] The ClojureScript Quick Start REPL Experiences are broken Oct 12, 2023
@PEZ
Copy link
Collaborator

PEZ commented Oct 12, 2023

Hi! Thanks for the report and for having a look at it fixing this. I'll have a look at that PR right away!

PEZ added a commit that referenced this issue Oct 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants