Auto-indent issue/question

[cjsauer]

Apologies if this is not the right place to be asking this, but I'm seeing a bit of odd behavior in my Clojure files regarding auto-indenting. I have tabstop=2, shiftwidth=2, and softtabstop=2 in my .vimrc file. When editing the following Clojure function, I can't seem to get indentation to work correctly for multiple-arity definitions.

(defn respond
  ([exchange body]
  ¦(respond identity exchange body))  ; <--- This should be one more space
  ([around exchange body]
  ¦(.sendResponseHeaders exchange OK 0)  ; <--- This should be one more space
  ¦(with-open [resp (around (.getResponseBody exchange))]
  ¦ ¦(.write resp (.getBytes body)))))

I've included the | characters to more easily show spacing. Notice how after the ([exchange body]\n, auto-indent is only placing a single space on the next line before the opening parenthesis, when it should actually be placing 2 spaces. Interestingly, this only seems to happen beneath the multi-arity definitions; everywhere else in my source is working correctly.

Any thoughts?

[kovisoft]

I think that's a bug in the indentation routine: it does not handle multi-arity functions, rather it treats the enclosing [] as if it was () (you can verify this: if you replace all [ with ( and all ] with ) and reindent the form then you get the same indentation). I'll try to fix it soon, thanks for reporting it.

[kovisoft]

Ah, I have just realized that you reported this issue for the paredit project, but the indentation is actually done in another script, depending on the value of set indentexpr?. If it is SlimvIndent(v:lnum) then it's done by the slimv plugin, otherwise it's probably done by vim's default clojure indenting script (e.g. GetClojureIndent()).

Either way, the problem is in the indentation plugin (and not in paredit). I fixed the problem in slimv in commit kovisoft/slimv@011e282 but I cannot fix vim's built-in indentation. As I see, vim's default indentation suffers from the same bug. So I suggest that you either use slimv (that includes paredit as well) or report this bug to the vim developers.