Not sure, but we could be using the calva.prettyPrintingOptions: maxLength option for this. There is no separate setting for that for the eval-replace case at least…

Thanks! The pretty-printing is nice otherwise it ends up in a huge line. I will try disabled it temporarily.

It worked 🙂

Setting maxLength to null should give you all the elements, but otherwise keep pretty printing things. Was that what you tried?

Yep

Howe do you switch to a cljs repl?

Clicking on the switcher in the status bar.

I merged a PR that might fix that some days ago. We should release that fix.

About the pretty printing. I'm not sure if it is supposed to work. But if you switch to client side pretty printing, that should work. (The calva pretty print engine.)

> I merged a PR that might fix that some days ago. We should release that fix. Sorry, was running a previous version. Updating to the latest, don't have that problem anymore.

Ah, so maybe we have released it. 😂

> But if you switch to client side pretty printing, that should work. (The `calva` pretty print engine.) It does, thanks. So, when working in cljs I should manually change the setting to calva. When working in clj I switch back to pprint?

I use calva all the time.

Right, sorry. What I'm really asking is: is that the only way to switch back and forth between them?

But I actually don't know if the server side engines should work.

If it is something we can't expect to work we could make Calva always use client side for cljs.

The only way to switch engines is through settings. I think there are extension that make toggling settings convenient.

Well, pprint works for me sometimes on the client side, but not always.

You could check the nrepl log and see if it has any clues.

I think it usually fails when there are tagged literals? Like in the image above.

Anyway, thanks for your kind and quick help!

Ah, yes, maybe when the data readers are not available to the JVM repl (where the nREPL server runs) it doesn’t work. On the Calva side of things that doesn’t matter, because it is all static.

Hello! I work with re-frame frequently lately. Can you describe what you mean by “integrate the repl”? What’s your JS/CLJS target? Is it a browser app, a nodejs app, a react-native app, something else (if there is)? In my case, with a react-native app, using shadow-cljs, I run Calva’s jack-in command and select shadow-cljs and the build I want to connect to. Once the repl starts, in order to evaluate code in the repl, your runtime needs to be connected. In my case, my runtime is my react-native app, running in an emulator (for example). Once the app is running, I can evaluate code from my editor, or from the repl prompt in the Calva output window.

Yes! This is exactly what I'm asking for. More specifically though, I'd like to know how you use the repl in actual development. I went through the calve hello_repl tutorial a couple of weeks ago and the stuff I learned seems cool. But I'm wondering if people actually use these things when hot reloading is already pretty immediate interaction.

Yes, it depends on what you’re trying to do perhaps, but the repl is still valuable even when using hot reloading. For example, I might pull in a library and want to test some calls using that library from the repl, without integrating the code into my app first.

Maybe I want to make direct http calls to some service to inpect the data I get back using the repl.

Or, I want to test a transformation with the repl before adding the transformation to my app code. For example:

(-> http-response
    :data
    (do-something))

And then once I have the final form I want the data in for my app, I copy the code into some function used by the app.

That makes total sense, thank you!

You’re welcome!

yes, 2.1.2

what is the code that doesn't work for you?

something like this:

hmm, is this better-cond.core/when-let?

according to this config it should work: https://github.com/Engelberg/better-cond/blob/4720bd8bcfd1adc1197b8d5f07873bc46008d333/resources/clj-kondo.exports/better-cond/better-cond/config.edn#L5

can you paste a repro of this so I can try it locally?

yes, this is my import

(:refer-clojure :exclude [sorted-map sorted-map-by sorted-set sorted-set-by first last when-let])
  (:require [clojure.data.avl :as avl]
            [better-cond.core :refer [when-let]])

ah

have you upgraded clojure-lsp to the most recent one?

or: can you paste the clojure-lsp and clj-kondo versions?

How can I know them from calva/vscode?

also, check if there is .clj-kondo/better-cond/better-cond

if not, then the config isn't imported

This is something that @U0ETXRFEW might now (the versions)

also, check if there is .clj-kondo/better-cond/better-cond

have you tried restarting your vscode?

well, that worked 😄

thanks!

🙌

I am having another problem now, it seems it’s linting it as a normal when-let now:

(ns volus.dev
  (:refer-clojure :exclude [when-let])
  (:require [better-cond.core :refer [when-let]]))

(when-let [a 1
           b 2]
  (println (+ a b)))

hmm, can you try {:lint-as {better-cond.core/when-let clojure.core/let}

in your own config

if that works, then this should be improved in better-cond

yes, that works

It seems better-cond config has a bug, here:

better-cond.core/when-let clojure.core/when-let

yes

my bad

I can open an issue/pr if needed

please

done, was a bit delayed by my mess on local git credentials https://github.com/Engelberg/better-cond/pull/21

thanks!

For example in this photo str has three different colors..

If I open a directory with less files, it seems to work. Could be a file watcher issue? Coworker in same folder doesn't have the issue though

Could this be a semantic tokens issue, @UKFSJSM38 ?

yeah, sounds like a conflict of semantic highlighting and maybe some other plugin

I was seeing this too, but it went away when I applied the fix here: https://clojurians.slack.com/archives/CBE668G4R/p1640048783488600?thread_ts=1640017230.483900&cid=CBE668G4R

Not sure it’s related, but you might see if it helps

I rolled back the versions and 2.0.201 (6months ago) is working as expected. I also tested 2.0.211 (3 months) and it still had the issue. I'll try the above fix this later tonight and report back. Thanks!

Just linking the two threads: https://clojurians.slack.com/archives/CPABC1H61/p1640530722287300