This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-02-13
Channels
- # beginners (50)
- # boot (27)
- # bristol-clojurians (7)
- # cider (30)
- # clara (1)
- # cljs-dev (130)
- # cljsrn (14)
- # clojure (179)
- # clojure-austin (6)
- # clojure-greece (2)
- # clojure-italy (4)
- # clojure-spec (19)
- # clojure-uk (54)
- # clojurescript (64)
- # core-async (3)
- # data-science (1)
- # datomic (66)
- # duct (11)
- # emacs (5)
- # figwheel (1)
- # fulcro (26)
- # funcool (7)
- # jobs (1)
- # jvm (6)
- # keechma (5)
- # lein-figwheel (5)
- # luminus (5)
- # lumo (1)
- # off-topic (93)
- # parinfer (37)
- # pedestal (15)
- # protorepl (10)
- # re-frame (42)
- # reagent (12)
- # shadow-cljs (71)
- # spacemacs (3)
- # specter (7)
- # vim (8)
- # yada (9)
@shaunlebron Would you care to comment on this bit of the thread here? https://groups.google.com/d/msg/cursive/ZJ4fcp3A988/erjJ1gFJBAAJ
ah, indenting docstrings!
i’ll think about it
yeah, I don’t like multiline strings in clojure
we have to preserve structure in front of a change, so we can’t shift multiline string indentation without breaking strings
it would be fine with docstrings
but there could be strings where that is not okay
Yeah, and the fact that the docstrings are not HTML or similar makes them a real pain to indent when displaying them.
yeah, that ship has sailed for clojure
i’ve seen new clojure-based lisps where they make indentation significant in multiline strings, seems to be a common pain point
That said, there are projects using markdown in their docstrings now, I’m planning to add an option to Cursive to display that.
@cfleming: i replied in the thread, thanks for the headsup
wish I could find that Lisp that had stricter multiline string indentation
i star too many repos
i couldn’t find a syntax guide for it
yeah, I thought it was carp, not sure though
There are quite a few now. Carp and Pixie are the ones that spring to mind, but I’m sure there are more. Oh and Hy.
it might be Hy
ha, I can’t spend anymore time tonight tracking this down
@shaunlebron is that transformChange will never return undefined?
@doglooksgood yeah, safe to say it’ll never be undefined
just guarding against bad plugin integration
I think when porting, is very important to know immutable/mutable of variables, and what will return null;
parinfer-jvm will be updated soon I think
you will be the third person this week who needs it