Clojurians Log v2

I guess the main problem for most people using the Clojure CLI is that they also using some aliases in their projects that CIDER obviously doesn't know about and they have to tweak the jack-in command manually. And if they happen to have another alias with a main in it, nothing good comes out of this. 🙂

cider-jack-in certainly produces better results out of the box for Lein and Boot, but that's not surprising as it was created with them and in mind, and the Clojure CLI support was just adapted to what we have. I'm still using Lein all the time, so I'm far from being an expert on the all the way people are using the Clojure CLI.

For me and since I begin with Clojure only for two years, I use both but 80% of time Clojure CLI, I I'm not part of the era where only Leiningen /Bootreigned 🙂 Perfect, thx @bozhidar for this clarifications, I better understand now. BTW thx for Cider, Projectile, and so on and on... 🙏

It's possible in theory, but it's not currently possible (in the sense that such a feature doesn't exist).

You can use eval-up-to-point to get the result of some specific part of the threading macro, though.

Never used eval-up-to-point before, it's nice! Thanks for the advice. 👍 @kevin586 With the argument, you can print the result in the current buffer, so then it can be a solution to manually comment the result in order to keep it and not to forget the output as you mention above.

Awesome, wasn’t familiar with the up-to-point functions, will check them out, thanks!

it does the trick. 👍

Notice that you can omit parentheses when functions in a thread macro have no arguments.