Clojurians Log v2

I feel like this should be in a suggestion box somewhere? It took me unusually long to find the answer to this in regular documentation when I first ran into it. Could, upon the detection of a macro with an unresolved symbol, this trigger some sort of suggestion box? Maybe that's a new feature suggestion for clj-kondo? Just sharing some thoughts

Yeah, I think if anything it would be a clj-kondo concern, but I'm not sure what more could be done to assist. CC @borkdude

Hi, seems that Ctrl-C Ctrl-D does not always kill a running process, for instance a large doseq or map with printing in it. It does recognize the command as it say 'interruption command finished (unknown results)'. Tried it both from the code editor and the REPL, same effect. (Calva 2.0.153 on Windows). Any Thoughts?

clj-kondo doesn’t provide the lsp here, right? It reports a linting issue. I think the more plausible options for providing tips on how to handel it are clojure-lsp, or Calva, through lsp middleware.

Another option is if we provide a quick-fix suggestion that adds the needed config.

@eric.uitbeijerse it is a known issue. The process is interrupted but the output window is not stopped in its printing of all the lines that have stacked up. Printing to an editor window is a bit slow.

I can’t figure out how to make it reproducible firmly, but it happens time to time to me. When I try evaluate some bad code as in the example above, I don’t see any feedback.

(ns app.foo
  (:require [app.bar :as bar]))

In the video zelark.maze doesn’t exist.

I think adding a link to the docs would best since there is often not one best way to solve a problem. Adding ignores all over the place would maybe prevent people from reading the docs

Ahoy! I have a pristine (I think) VS Code and Calva installation, and the "Calva: Connect to a Running REPL Server, not in project" command yields Cannot read property 'toString' of undefined. Any ideas what might be wrong?

https://github.com/BetterThanTomorrow/calva/issues/855

You can work around some, afaict, by having a project folder opened in vscode.

Thanks! My google-fu wasn't strong enough to find that issue.

Unless we count asking in here as part of your google-fu. 😃

Let's merge #972 & #956 please!

Leaving these up to @pez as he's the one reviewing/working on them. I think he'll be getting to them soon.

956 is made by him and needs to be approved by someone else

I'm getting to them. Have a birthday to celebrate here tonight (not mine, my daughter's), but intend to have a look before bedtime. 😍

@claudius.nicolae I know. We've discussed if/how we should notify users of default keybinding changes, so I think that's been a bit of the delay, but I think it'll be going out soon. :simple_smile:

Calva version 2.0.154 is released! 🎉 :calva: :clojure-lsp: • Fix: https://github.com/BetterThanTomorrow/calva/issues/971 • Update cider-nrepl to 0.25.8 • Update clojure-lsp to 2021.01.26-22.35.27 @zelark and @grumplet The cider-nrepl update may fix your issues, please test it out. @plexus and others who experienced the comment issue, Calva should now use ;; always.

Over the last few weeks I’ve had this bug with Calva:

When I Jack In, it asks me for the repl port.

It used to just connect itself

now I need to copy the port from the terminal and paste it in the dialog box at the top

Am I doing something wrong?

Fix should be released soon https://github.com/BetterThanTomorrow/calva/pull/972

https://i.redd.it/z8gc9b7163z41.png 😅

Awesome, thanks!

This is so true ☝️ :rolling_on_the_floor_laughing:

Hi, Is it at all possible to use both Clojure CLI and Shadow CLJS in one window? I’m using Fulcro, so my files are right next to each other. I finally decided to jump back to VSCode from Emacs (Loved emacs, but damn, VSCode is so much faster on my macbook), and this is the only thing blocking me 😞