This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-03-18
Channels
- # beginners (22)
- # boot (12)
- # cider (3)
- # cljs-dev (12)
- # cljsrn (8)
- # clojure (101)
- # clojure-nl (5)
- # clojure-russia (13)
- # clojure-spec (5)
- # clojure-uk (15)
- # clojurescript (158)
- # cursive (5)
- # datascript (16)
- # datomic (8)
- # hoplon (11)
- # lumo (33)
- # off-topic (3)
- # om (25)
- # parinfer (1)
- # pedestal (8)
- # protorepl (4)
- # re-frame (8)
- # reagent (5)
- # specter (18)
- # sql (1)
- # testing (11)
- # timbre (1)
- # unrepl (2)
- # untangled (1)
@cgrand: > I've come up with `"\uE5CA\n[)\"[)" as an escape sequence with low probability of buffering and not being valid input. Why that sequence in particular, any reason or just a combination of unlikely characters?
@cfleming I'm backpedaling a lot on all input aspects. I'm on vacation this week, hopefully I'll get some hammock time. However there was a logic behind this escape sequence: first a rare private character to limit buffering. Then a new line in case we are in a comment. Then mismatched parens to be sure it's invalid clojure then a double quote in case we were in a strong. And mismatched parens again.