• While typing, the docstring aligns with the parameters. • If the cursor is anywhere within the parentheses that wrap the method definition, then calva-fmt.formatCurrentForm follows the same rule, and aligns the docsctring to the params. • This only applies to the method expression the cursor is inside of. Move the cursor inside a different method expression, and run calva-fmt.formatCurrentForm to also format that form as described above, not effecting alignment of any other method. • Move the cursor to where it is outside of any method expression and run calva-fmt.formatCurrentForm and a different rule takes over. All the docstrings align to the second character of the respective method name. • Same with other format-triggering events (such as paredit.dragSexpForward). So long as the cursor is not within an expression defining a method, all the docstrings align to a +2 character indentation.

; | for cursor

(defprotocol Foo
  (method [_] |"docstring"))

; <Enter>
(defprotocol Foo
  (method [_]
         |"docstring"))

; <calva-fmt.formatCurrentForm>
(defprotocol Foo
  (method [_]
         |"docstring"))

; <move cursor>
(defprotocol Foo
 |(method [_]
          "docstring"))

; <calva-fmt.formatCurrentForm>
(defprotocol Foo
 |(method [_]
    "docstring"))

; <move cursor>
(defprotocol Foo
  (|method [_]
     "docstring"))

; <calva-fmt.formatCurrentForm>
(defprotocol Foo
  (|method [_]
           "docstring"))

I wonder if maybe formatCurrentForm doesn’t have knowledge that the “current form” is inside a defprotocol form when the cursor is inside the method form… An issue is welcome. @U0ETXRFEW might have an idea what’s going on.

What happens if you press tab? You might need to go to a level above but it usually fixes all indentation issues.

It already changes the brackets so that it becomes a top level form, TAB doesn't fix it

Never seen this. Which versions of VS Code and Calva are you using, @U24MDANHY? Can you reproduce it in all files, or is it only in some?

It happened to me every single time for every clojure file I ever cared to open/edit

vscode 1.73.1 on ubuntu Not sure how to see the calva version (thanks vscode) - but it's supposedly the latest in the vscode store or whatever, I haven't held it back or anything, and it doesn't tell me to update it

What's your VS Code settings for on-type formatting?

disabled, but it does tell me it's (Modified elsewhere) and when I hover it tells me that Clojure has different defaults

Calva reports it version in the Output pane Calva says. Also Clicking the Calva entry in the Extensions pane should show it.

Calva version used: v2.0.320
clojure-lsp version used: 2022.11.03-00.14.57
clj-kondo version used: 2022.11.02

Can you try enable it?

Enabled, still not working

Hold on, posting a screencast

Do you use some other Clojure extension?

Well, Peek segfaults so no screencast for us 😞

I don't, but I do use a nontrivial amount of extension, it's not impossible that there's a collision of some sort

There's an extension named Chronicle which is excellent for recording VS Code.

Prettier is disabled on cljs files

Can you try if you have the same issue in VS Code Insiders?

Are you using VIM?

(The extension)

I do not

Please file an issue using VS Code's Help-menu item for it. It will attach some system information and such.

> It already changes the brackets so that it becomes a top level form, TAB doesn't fix it This is a clue I think. I have never seen Calva do this, and am thinking it could be some other extension at work. Could of course also be a Calva bug.

A broken Parinfer extension could do something like that maybe...

It should be noted that I have "Parinfer </> Smart" mode enabled, it might have something to do with it

That's probably it.

Yeah, in paren mode it works

So it's an issue with that extension. There's a #C0F2A0MJN channel where you can ask about it.

I should really get more into paredit and put parinfer behind 😢 - but it's too different from what I know and it's a lot of things to learn at once 😅

😃 You can have paren mode enabled and learn Paredit in your own pace.

The issue is very unlikely to be fixed anytime soon. No-one knows how to implement Parinfer smartmode on VS Code. I have been the closest, I think, but had some other problems with that so had to pause that work.

:saluting_face: Thank you for your work, just being able to properly edit clojure in vscode makes it so much more accessible ❤️

You are welcome, @U24MDANHY! ❤️