Fork me on GitHub
#cider
<
2021-10-19
>
nha19:10:21

I’m not sure if I should ask here or in #nrepl When upgrading my cider/cider-nrep dependency I loose the logs. The last version that works is “0.25.11”, and starting from “0.26.0" I just don’t have the logs anymore. I had a quick look at the changes and nothing jumps out - is it something known?

cider/cider-nrepl {:mvn/version
                           ;; "0.25.4" = OK
                           ;; "0.25.10" = OK
                           ;; "0.25.11" = OK
                           "0.25.11"
                           ;; "0.26.0" = KO
                           ;; "0.27.2" = KO
                           }
In case it matters, I am using deps.edn+`clojure.tools.logging` +`log4j2`

vemv19:10:14

there was an issue related to *out* but that was fixed in 0.27.1

vemv19:10:48

if possible create a repro with an analog setup (deps.edn, logback.xml etc) and create a GH issue, LMK :) (a part of the repro is that it should be visible over iTerm - adding Emacs to the mix makes things less certain)

nha19:10:10

I am looking at logs in iTerm actually - I tried “0.27.2” so it should not be that. I’ll wait a bit before jumping on a repro in case something knows what it is but I agree that will make it easier if that’s not the case.

vemv19:10:12

I'll re-review a suspicious commit (various added type hints)

🙂 1
vemv13:10:23

checked out, nothing seemed off would gladly inspect a GH issue/repro

nha16:10:47

Noted. I'll se if I can make a repro

dpsutton20:10:19

helpful function inspired by calva's latest feature:

(defun personal/insert-comment ()
  (interactive)
  (end-of-defun)
  (insert "\n")
  (insert "(comment\n  )\n")
  (clojure-backward-logical-sexp)
  (forward-char 1)
  (clojure-forward-logical-sexp)
  (insert "\n")
  (indent-according-to-mode))

dpsutton20:10:49

if you're in a form, add a new comment form after it for easy repling

Derek20:10:56

Put a comma before the trailing paren 🙂

dpsutton20:10:17

for what purpose?

Derek20:10:41

It keeps paredit from collapsing the trailing paren up a line

Derek20:10:05

type ‘)’ and paredit will join the following line if present

dpsutton20:10:08

you probably mean parinfer?

Derek20:10:59

_ is cursor position

clj
(comment
  (execute-some-fn)_
,)

tvaughan11:10:36

I use 42 :)

dpsutton20:10:44

oh i see. i guess i never type closing parens

Derek20:10:08

a useful function — didn’t mean to derail

dpsutton20:10:45

no worries. i honestly didn't know about how paredit did that but i honestly never type closing parens ha

pez20:10:08

That's another Calva feature, actually, to not fold the trailing paren in a rich comment form.

Derek20:10:27

wonderful