This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-08-23
Channels
- # announcements (2)
- # beginners (246)
- # boot-dev (1)
- # braveandtrue (3)
- # calva (13)
- # cider (26)
- # cljs-dev (6)
- # clojure (75)
- # clojure-finland (4)
- # clojure-germany (39)
- # clojure-italy (1)
- # clojure-mexico (1)
- # clojure-nl (14)
- # clojure-spec (61)
- # clojure-uk (104)
- # clojurescript (125)
- # cursive (20)
- # datomic (1)
- # emacs (2)
- # figwheel-main (91)
- # fulcro (29)
- # graphql (9)
- # jobs (3)
- # jobs-discuss (9)
- # juxt (13)
- # liberator (2)
- # luminus (1)
- # off-topic (15)
- # parinfer (8)
- # re-frame (70)
- # reagent (35)
- # reitit (24)
- # remote-jobs (5)
- # ring-swagger (3)
- # shadow-cljs (127)
- # spacemacs (34)
- # yada (6)
Unsure if this is the right place to ask (it probably isn't), but I'm having a heck of a time getting auto-indenting when I hit enter to work. i.e., I type (let [v 42
and hit enter, and instead of going under the v, VSCode puts me at the beginning of the line. Applicable settings:
"calva.autoConnect": false,
"calva.testOnSave": false,
"calva.fmt.autoAdjustIndentOnNewLines": true,
"calva.fmt.indentation": true,
"[clojure]": {
"editor.formatOnType": true,
"editor.autoIndent": true,
"editor.formatOnPaste": true
}
This is the right place to ask that. And that looks like a bug. And it must be pretty recent, because that used to work!
I am currently often testing Parinfer and then need to have this auto-indenting switched off, so have missed the issue. Will investigate. Thanks for headsup!
I found the bug. When trying to prepare Calva Formatter for coexistance with Parinfer I accidently almost disabled the auto-formatting completely. I wonder how many people have been inconvenienced by this. Very, very good that you let me know. I have now released a fixed version.
Must look into how to test this kind of thing automatically. Once I figure out the mechanics it would be caught by a simple smoke test before releasing.