Marc O'Morain
Marc O'Morain
Yup, I had the same issue. $ sudo cpanm Error fixed it for me.
My current work around is comment out `:penantic? :abort` when loading a project in `code`.
Another option could to be to start leiningen with a specific profile when starting from vscode. Then I could add a custom setting in my `~/.lein` folder for this: ```Clojure...
We set this option on our projects in project.clj This means that if our projects depend on any versions of nrepl or clj-fmt that are different from the versions that...
If we invoke the repl with `lein repl :headless :vscode` then users could put any special lein options that they would like into a `:vscode` profile in `~/.lein/profiles.clj`
As it stands, `lein repl` uses the `:repl` profile in `~/.lein/profiles.clj`
# Before  # After 
Hrm, maybe the sort stack trace is not such a good idea. It makes sense for syntax errors, but not for the results of eval, where you want to see...
I think this PR needs to be re-done, since it hides the stack-trace of evaluation errors, which makes debugging problems really hard. (I want to hide the stack trace of...
Yeah, it seems possible based on this module: https://github.com/snoe/node-cljfmt/tree/master/bin