You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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
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
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.
The text was updated successfully, but these errors were encountered: