Fork me on GitHub
#cider
<
2017-12-06
>
chrisblom09:12:19

does cider 0.15 support namespaced maps?

chrisblom09:12:39

in 0.14 if i C-x C-e #:person {:name "chris"}, it just returns {:name "chris"}

chrisblom09:12:26

while (read-string "#:person{:name "chris"}") returns #:person{:name "chris"}

grzm18:12:22

Does that depend on the Cider version or the Clojure version?

grzm18:12:53

FWIW, in 0.16:

boot.user> {:foo/bar :a :foo/baz :b}
#:foo{:bar :a, :baz :b}
boot.user> #:foo{:bar :a, :baz :b}
#:foo{:bar :a, :baz :b}

grzm18:12:07

Oh, I see what you mean about using cider-eval-last-sexp:

{:foo/bar :a :foo/baz :b};; => #:foo{:bar :a, :baz :b}
#:foo{:bar :a :baz :b};; => {:bar :a, :baz :b}

grzm18:12:39

Yeah, there's something wonky going on there.

gonewest81819:12:57

@grzm I have a pull request open to pretty-print the last sexp to comment. Check the cider project on GitHub.

grzm19:12:58

@gonewest818 cool. Does this always print the result on the following line? I'd like an option to append to the current line. It looks like it is always the following line (which makes sense for multi-line comments), if I'm reading the commit correctly.

gonewest81820:12:54

I can’t remember but I thought the behavior was it inserts at the point, so if the point is on a new line then it inserts from there. when I get to a laptop I can check.

grzm20:12:16

You're right. It does look like it inserts at point. It does look like it indiscriminately adds a newline. It would be nice if there were only one line to the result that it wouldn't do that, or at least make it optional.