This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-04-09
Channels
- # admin-announcements (1)
- # boot (225)
- # braid-chat (1)
- # cider (25)
- # cljs-dev (35)
- # cljsrn (1)
- # clojars (6)
- # clojure (81)
- # clojure-berlin (1)
- # clojure-dev (21)
- # clojure-france (2)
- # clojure-japan (6)
- # clojure-poland (1)
- # clojure-russia (10)
- # clojure-uk (3)
- # clojurescript (121)
- # code-reviews (1)
- # core-async (4)
- # core-logic (2)
- # cursive (15)
- # datomic (8)
- # hoplon (4)
- # jaunt (112)
- # jobs-discuss (35)
- # om (41)
- # parinfer (8)
- # re-frame (3)
- # reagent (4)
- # ring (2)
- # untangled (38)
hey @snoe, looks good
looks like your code isn’t inserting extra tab stops though for the 1-space or 2-space indentation levels, right?
from the readme section https://github.com/shaunlebron/parinfer/tree/master/lib#adding-parinfer-to-an-editor, item 5.iii
These returned tab stops only represent open-paren positions, so you need to insert extra tab stops depending on your desired indentation conventions. For example, you can add a tab stop to represent a one-space indentation after every [, a two-space indentation after every (, or even get fancy by reading the text that comes after ( to determine context-specific indentation, as is common in Lisp.
I should probably clarify that with an example
(let [foo 1
| |
bar 2])
(let [foo 1
| | ||
bar 2])
I supply the tab stops in the first example, and you have to add the extra ones depending on your desired indentation conventions