Fork me on GitHub
#cider
<
2019-04-16
>
benedek05:04:19

this kinda boils down to eval or not eval

benedek05:04:12

and i tend to agree that not eval is the way with the caveat that a not evaling backend needs to do a lot to be complete, reliable (in @dominicm terms)

benedek05:04:11

i was possibly not clear when comparing this to cider. the real edge here is the not evaling analyzer

benedek06:04:36

i might give this rewrite-clj based analyzer a go

benedek06:04:09

see you guys in 3 months :)))

yuhan10:04:34

Is there some sort of configuration to control the (pretty) printed representation of records? In particular I'd like to abbreviate the full namespace name as it tends to take up a lot of horizontal space

yuhan10:04:12

eg.

(ns some.arbitrary.deeply.nested.namespace)

(defrecord Foo [bar1 bar2])
(defrecord Bar [bar])

(->Foo
  (->Bar [1 2 3])
  (->Bar [4 5 6]))
;; => #some.arbitrary.deeply.nested.namespace.Foo{:bar1 #some.arbitrary.deeply.nested.namespace.Bar{:bar [1
;;                                                                                                     2
;;                                                                                                     3]},
;;                                             :bar2 #some.arbitrary.deeply.nested.namespace.Bar{:bar [4
;;                                                                                                     5
;;                                                                                                     6]}}

yuhan10:04:17

it makes the actual content of the maps very hard to make out

benedek10:04:19

played with clojure-lsp a bit. seems to be working fine together with cider actually. eg. without jacking in it gives you go to definition, find usages, rename and joker like linting. pretty nice

benedek10:04:06

https://github.com/snoe/clojure-lsp/issues/27 is annoying tho, and should be a small fix really

benedek10:04:34

basically means that you can’t jump into dependencies which i do all the time

benedek10:04:30

not quite sure how to run the refactorings, this executecommand thing is a bit cryptic

cddr13:04:06

I've recently started seeing "No linked cider session" when I try to inspect the stacktrace of an error. emacs version: GNU Emacs 26.0.90 (build 1, x86_64-apple-darwin13.4.0, NS appkit-1265.21 Version 10.9.5 (Build 13F1911)) of 2017-10-11 cider-version: CIDER 0.22.0snapshot (package: 20190302.114)

bozhidar14:04:52

> Is there some sort of configuration to control the (pretty) printed representation of records? In particular I’d like to abbreviate the full namespace name as it tends to take up a lot of horizontal space (edited)

bozhidar14:04:35

@qythium Don’t think so. I doubt any pretty-printer does something special with those namespaces and CIDER certainly doesn’t do anything with them as well.

bozhidar15:04:08

> I’ve recently started seeing “No linked cider session” when I try to inspect the stacktrace of an error.

bozhidar15:04:49

@cddr How recently? I don’t recall any changes related to this for quite a while.

cddr15:04:38

Just started seeing it today but this is probably just the first time I've tried to use the feature since upgrading to the versions above.

cddr15:04:40

If I do sesman-info in a clojure buffer, I see the expected (only current) connection, but in the test-report-buffer, if I do the same, I don't see any connections

cddr15:04:05

Seems I can manaully link it using sesman-link-with-buffer