Clojurians Log v2

I’ve only tried using the same nrepl server.

care to share the deps config? ..when I start Calva it show the localhost:port in the output (I always select deps.edn and don't choose any custom names configs in the check box list). I always assumed this was the nREPL listener address used by Calva. As the port changes each time I start the REPL, I'm a bit confused as to how this should be setup.

It sounds like you have the correct mental model. I haven’t played with it much and don’t really have a setup. I tested it with CoPilot and my .vscode/mcp.json looked like so:

{
  "servers": {
    "clojure-mcp": {
      "type": "stdio",
      "command": "sh",
      "args": [
        "-c",
        "cd ${workspaceFolder} && clojure -X:mcp :port 54501"
      ]
    }
  }
}

Ugh, sorry, got pulled away yesterday. Restarting the editor does not work. Renaming to cljfmt.edn also does not work.

Is there a place where Calva logs info? Looking at the “Output” panel under “Calva says”, I don’t get much info — it doesn’t appear to be a place where logs are sent.

I have opened a code workspace that currently looks like the below. I’ve tried removing the calva.fmt.configPath key. Still no dice.

{
  "folders": [
    {
      "path": "."
    },
    {
      "path": "code",
      "name": "Code"
    }
  ],
  "settings": {
    "editor.formatOnSave": true,
    "editor.formatOnPaste": true,
    "editor.defaultFormatter": null,
    "calva.fmt.configPath": "cljfmt.edn"
  }
}

Out of curiosity, I just tried opening another project without the code-workspace. e.g., just a regular, flat Clojure project. I added a cljfmt.edn and ran format document. Nothing. It’s like some knob somewhere is turned off.

@phill suggested checking the developer tools. Which you do from the Help menu of VS Code.

Iiuc, Calva could handle that much better.

Oh, yeah - great idea! Do I need clojure-lsp?

Seems expected

Overwriting grammar scope name to file mapping for scope source.clojure.
Old grammar file: file:///Applications/Cursor.app/Contents/Resources/app/extensions/clojure/syntaxes/clojure.tmLanguage.json.
New grammar file: file:///Users/kenny/.cursor/extensions/betterthantomorrow.calva-2.0.516/clojure.tmLanguage.json

All red herrings. 😃

@phill says that the error message was about \w not being a valid escape character. Since the regex there is actually a string you need to escape the escape: \\w.

For some reason my console does not have that error though. Tried, nonetheless. Same - no format change. Did reload window. Also restarted.

{:remove-surrounding-whitespace? true
 :remove-trailing-whitespace? true
 :remove-consecutive-blank-lines? false
 :insert-missing-whitespace? false
 :indent-line-comments? true
 :indents {#re "^\\w" [[:inner 0]]}
 :test-code
 (concat [2]
         (map #(inc (* % 2))
              (filter #(aget sieved %)
                      (range 1 hn))))}

Wait - that is kind of interesting though. Is Calva ignoring my cljfmt.edn file? Perhaps it should have printed the error and it didn’t because it isn’t finding the cljfmt.edn file for some reason.

clj-kondo complains about #() not being allowed in edn. Perhaps reading this file is failing because of this test, haha

Could be. I don’t recall what we use for parsing, right now.

Another update: if I run clj -Tcljfmt check on the CLI it will report everything is formatted correctly. If I go into the file and run the format document command, numerous changes will be made.

It’s really like the cljfmt.edn file is ignored.

When I try it (and I now realize it is I who have written the example … facepalm ) I need to fix both the regular expression and the #(). Then it works. Probably cljfmt is less picky than Calva.

{:remove-surrounding-whitespace? true
 :remove-trailing-whitespace? true
 :remove-consecutive-blank-lines? false
 :insert-missing-whitespace? false
 :indent-line-comments? true
 :function-arguments-indentation :cursive
 :indents {#re "^\\w" [[:inner 0]]}}

The reason here is that at some point we changed it so that Calva is using clojure.edn/read-string instead of clojure.core/read-string. So we broke the example.

If you have the time , you are welcome to PR a working example and a note about the discrepancy between Calva’s and cljfmt’s treating of the file.

It still does not seem to follow the rules when formatting the doc, tho.

The setup looks like this. I wonder if it has to do with the monorepo setup here.

.
├── bb.edn
├── cljfmt.edn
├── code
│   ├── apache-math
│   ├── date
│   ├── distributions
│   ├── math
│   ├── mcp
│   ├── models
│   ├── neanderthal-matrix
│   ├── solvers
│   ├── test
│   ├── tree-ui
│   └── utility-belt
├── Provisdom.code-workspace
└── repos.edn

Running cljfmt check in one of the libraries, say utility-belt, states the code is formatted correctly. Opening a file in VSCode, in again say utility-belt, and running format document will change the formatting. Does Calva stop checking for cljfmt.edn once it hits any workspace root? e.g., we first check utility-belt (none found), then code (none found), and stop since it’s a workspace root.

Ah, that seems to be it! If I place the cljfmt.edn file inside of the code directory, it works!

Think I’m getting closer! If I explicitly set the configPath, it will work.

"settings": {
    "editor.formatOnSave": true,
    "editor.formatOnPaste": true,
    "editor.defaultFormatter": null,
    "calva.fmt.configPath": "/Users/kenny/github/provisdom/all-repos/cljfmt.edn"
  }

{
  "folders": [
    {
      "path": ".",
      "name": "all-repos"
    },
    {
      "path": "code",
      "name": "Code"
    }
  ],
  "settings": {
    ...
    "calva.fmt.configPath": "${workspaceFolder:all-repos}/cljfmt.edn"
  }
}

I’ve run across that too. Calva only looks in one place, and cljfmt looks recursively somehow.

I see. Does Calva support VSCode variable references?

Not if they arrive unresolved.

That must be what’s happening. Why would a variable arrive unresolved?

I don’t know how this is supposed to be resolved. But seems like we can’t expect it to work when used in a Calva setting like that. In tasks.json it is resolved, and the setting is then not using it.

So, an absolute path is probably what is needed.

I am unaware of the setting for the location of cljfmt.edn. I just put cljfmt.edn in the project root, I mean right beside project.clj.

See if it helps naming it cljfmt.edn. I doubt this is the problem, but anyway, let’s confirm.

If it's not in the workspace you have to restart calva to get it to read the cljfmt.edn file, and restart if you make any changes. The automatic re-read and reload only happens if the cljfmt.edn file is in the workspace.

That tripped me up when I first configured it and put the file in ~/.cljfmt.edn

I opened Developer Tools (Help -> toggle developer tools) and saw the following message: " ERR Unsupported escape character: \w.: Error: Unsupported escape character: \w."

I have it like this:

:indents {#re ".*" [[:inner 0]]

Here is my entire config:

{:remove-surrounding-whitespace? false
 :remove-trailing-whitespace? true
 :remove-consecutive-blank-lines? false
 :insert-missing-whitespace? false
 :sort-ns-references? true
 :function-arguments-indentation :cursive
 :indents {#re ".*" [[:inner 0]]}
 :extra-indents {->         [[:default 1]]
                 ->>        [[:default 1]]
                 cond->     [[:default 1]]
                 cond->>    [[:default 1]]
                 some->     [[:default 1]]
                 some->>    [[:default 1]]
                 as->       [[:default 1]]
                 str        [[:default 1]]
                 or         [[:default 1]]
                 and        [[:default 1]]
                 not        [[:default 1]]
                 do         [[:default 1]]
                 doall      [[:default 1]]
                 dorun      [[:default 1]]
                 doseq      [[:default 1]]
                 dosync     [[:default 1]]
                 dotimes    [[:default 1]]
                 doto       [[:default 1]]
                 =          [[:default 1]]
                 when       [[:default 1]]}}