This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-02-18
Channels
- # admin-announcements (3)
- # announcements (7)
- # aws (1)
- # beginners (76)
- # boot (340)
- # cider (9)
- # clara (35)
- # cljs-dev (7)
- # cljsjs (16)
- # cljsrn (11)
- # clojars (1)
- # clojure (192)
- # clojure-dev (6)
- # clojure-madison (8)
- # clojure-russia (373)
- # clojurebridge (1)
- # clojured (9)
- # clojurescript (172)
- # community-development (1)
- # core-async (2)
- # cursive (7)
- # data-science (2)
- # datomic (12)
- # devcards (1)
- # dirac (63)
- # emacs (3)
- # events (10)
- # gsoc (3)
- # hoplon (1)
- # jobs (1)
- # juxt (20)
- # ldnclj (4)
- # lein-figwheel (12)
- # leiningen (1)
- # off-topic (21)
- # om (232)
- # onyx (64)
- # parinfer (8)
- # proton (21)
- # re-frame (8)
- # reagent (1)
- # ring (3)
- # ring-swagger (3)
- # slack-help (4)
- # spacemacs (6)
- # testing (3)
parinfer 1.6.0 is published to npm
returns the cursor position (so that modifications to a line shift the cursor appropriately)
for users, cursorX
is always returned from the mode functions, so always update the cursor with that
for porting, see the following pull request, which splits the code/tester/cases/doc changes into individual commits for easy reading
hey @shaunlebron i tried out the new version was wondering if this was intended: parinfer.indentMode("(", {cursorLine: 0, cursorX: 1})
returns {text: "()", cursorX: 2}
(among other things). that seems to mean that typing an open paren moves the cursor after the closing brace.
@sekao thanks. def a bug
looks like i missed a basic use case. will add a test case for that, and actually play with it in an editor to see what else i missed