zprint is not the default pretty printer, but you can make Calva use it via a setting: https://calva.io/pprint/#configuration

@U9A1RLFNV sorry, I was confused by: > Client side always uses `zprint`. now I tried setting the printEngine to “zprint” or “calva” and jacking again, just to be sure, but I still don’t get new behavior. here’s the relevant part of my settings.json:

"calva.prettyPrintingOptions": {

        "enabled": true,
        "width": 120,
        "maxLength": 100,
        "printEngine": "zprint"
    }

Thanks. Can you describe in more detail what is actually happening and what is expected via example output?

(require '[zprint.core :as zp])
(def example {:this :is :a :test :it :is :only :a :test :foo :bar :baz :but :better :if :it :does :not :fit :on :one :line})
example
;; => {:a :test, :bar :baz, :but :better, :does :not, :fit :on, :if :it, :it :is, :one :line, :only :a, :test :foo, :this :is}
(zp/zprint example)
;; => {:a :test
 :bar :baz
 :but :better
 :does :not
 :fit :on
 :if :it
 :it :is
 :one :line
 :only :a
 :test :foo
 :this :is}

Hmm, please file an issue so we can track it there.

sure, thanks for the help and all the work!

Sounds like something is going wrong. Can you provide code for reproducing the issue? A full project may be more helpful, but we could start with just code.

On my machine I can just create an empty folder and then jack in > babashka in there to reproduce this... If I try to eval this form in the repl window nothing happens.

If I try the same thing in the bb repl in a terminal:

user=> (asdf)
Could not resolve symbol: asdf [at <repl>:1:2]

And the jack-in terminal is also empty

Which bb version?

I fixed something in 0.6.7, if you’re not using that, please upgrade

$ which -a bb
/usr/local/bin/bb
$ bb --version
babashka v0.6.7

I see the same behaviour. Also with nbb. I think this is on Calva, @UUKPL2T9C. Please file an issue.

There is some option for making bb output nrepl messages. nbb does it by default. And if you toggle on Calva: Diagnostics Toggle nREPL messages Enabled (or something like that) and paste the relevant chunks with some extra context in the issue, we will have some clues to work from.

I’ve opened it here https://github.com/BetterThanTomorrow/calva/issues/1413 🙂

Thanks! Can you also add the nbb/bb nrepl logs?

How can I get them? I’ve added the nREPL diagnostics logs.

Do you mean lein new <project>? I can’t seem to reproduce the issue. Does it happen consistently for you?

Can you try with v2.0.226 and see if it is something up with the new version?

Also, that syntax highlighting, is it wonky before you try to evaluate? Can you describe the steps until you see weirdness? What OS are you using?

yes, I meant lein new <project>

With .228 (after the revert), I’m not having any issues

The wonk shows up as soon as I edit a file, but not before

and then once I edit, it’s permanently in wonk mode

(I do have a paren-coloring extension installed as well: https://marketplace.visualstudio.com/items?itemName=CoenraadS.bracket-pair-colorizer-2)

Is it a file with CRLF line endings, @calen.pennington?

I’m using OSX, so I’d assume no, although I haven’t explicitly checked

If you have the project available, please check. I can only reproduce something similar with CRLF files (but also only in the output/repl window) so it might be two different bugs).

The VS Code status bar shows this by default, btw.

@U9A1RLFNV @U0K592YDP @U0DAFTH63 and anyone else that might have latest dev checked out. Please not that I have force pushed a revert to the commit where we merged @U0K592YDP fixes to test query. I am so sorry for the inconvenience! But it seems otherwise this parinfer problem would block other improvements.

@U9A1RLFNV please also note that published is still at the experiment, a commit ahead even. I published a notice on the Parinfer page about the revert. Let’s see if we can fix the issues quickly or if we’ll need to revert published as well.

I was having an issue with the backspace keybinding not working on dev last night.

I think I know what that could be about. And it is probably easy to fix. Those highlighting issues on @calen.pennington’s screenshot are super worrying though…

Please update this issue with any further info you might have, @U0K592YDP https://github.com/BetterThanTomorrow/calva/issues/1409

😀

Will you believe that I felt impaired just now when 228 was automatically installed and I didn’t have these new features anymore?

Please, please run with 227, @UGNFXV1FA! I know you’ve been testing all sorts of versions of it up till now and it has been super valuable. I promise not to let this setback knock this effort out. I’ll continue trying to figure it out. I had hoped I could spend the time on refining the Parinfer stuff, but that’ll have to wait.

I am @U0ETXRFEW no worries, that’s what I meant with the screenshot 🙂 I’m just encouraging you and saying that I can be patient ❤️

Note to self: That description of the Parinfer feature needs revisiting.

It’s Calva. Or, rather cljfmt probably doesn’t handle non-Clojure content very well. Can you test with cljfmt from the command line and see what it does? Could also be that newer versions than the one Calva uses handles it better. Regardless, we should be able to work around it. What does “Format current form still works” mean here? That you can format some form in the document still? Calva will only send the current enclosing form to cljfmt with that command, so the shebang won’t be a problem. However, using the command at the top-level of the document (between some top level forms) should also not work. Please file an issue with your findings.

This line in particular or #! lines in general?

The latter - #! Is special cases to act like ;

TIL. Very good to know!

Specifically to allow this!

This could mean that it is not a cljfmt issue. But also that it is an issue in the old version of cljfmt that Calva uses.

Okay, so it seems calva is using cljfmt 0.6.3? I tested manually with 0.6.3 and indeed

Failed to format file: test.clj
clojure.lang.ExceptionInfo: Invalid symbol: /usr/bin/env.
1 file(s) could not be parsed for formatting

I opened https://github.com/BetterThanTomorrow/calva/issues/1414 🙂

Awesome. Then we know a way to fix it. 😃

Not currently. But I’m curious now about why you wonder. 😃

Well, the application I work on uses taoensso.timbre and this logs to output. In production and on our dev server this log is caught by supervisorctl. But, when I work locally the log gets spammed into the JackinTerminal which does not allow a full history. And I need some values that are flying by haha

Please file a feature request about it.

For now I think you’ll need to start the REPL yourself and tee out the log. There is a command for copying the command line that Calva uses for jack-in.

Yes.

The Connection Log is a bit of a misnomer. Or, rather the way we use it is not complete. It only logs messages we get from the ClojureScript repl session while it is connected.

Calva says is a bit more of a general messaging log.