Fork me on GitHub
#cider
<
2020-01-21
>
bozhidar07:01:59

I guess it’s best to ask @robertkrahn about this. Everything seems fine to me, but I recall there were some issues with shadow and suitable.

andrea.crotti12:01:39

any clue why cider would shadow a local-set-key I've added? I have something like

(defun ca-cider-or-dumb-jump ()
  (interactive)
  (if (cider-connected-p)
      (cider-find-var)
    (dumb-jump-go)))

(add-hook 'clojure-mode-hook
          (lambda ()
            (setq-local cider-repl-use-pretty-printing t)
            (local-set-key (kbd "M-.") 'ca-cider-or-dumb-jump)

andrea.crotti12:01:07

but M-. is still always just cider-find-var

andrea.crotti12:01:10

M-.             ca-cider-or-dumb-jump
  (that binding is currently shadowed by another mode)

andrea.crotti12:01:42

does the order matter somehow? I don't think I ever noticed an issue like that

tatut14:01:07

I too often accidentally print or otherwise log huge datastructures or otherwise enormously long lines... bringing emacs to its knees. is there a way to limit printing to something sensible (like max 2k line length)

tatut14:01:52

I do remember seeing some truncation of output sometimes

tatut14:01:49

examining the *nrepl-messages ...* for example the "eval" response messages is something I'd like to truncate

tatut14:01:30

is there a client implementation in CIDER for this closed issue? https://github.com/nrepl/nrepl/pull/79

tatut14:01:37

can't find anything with apropos

bozhidar15:01:12

Yeah, there is. The default however is 1MB of output.

Eric Ihli16:01:05

I had something semi-working before. I think it was a comint filter function that truncated stuff. Problem is it messed up syntax highlighting in my buffer because it might truncate after an opening quote but before a closing quote. I gave up. But if someone has a solution to that then I think the comint filtering would work.

tatut20:01:11

what's the name of the config? I couldn't find it

tatut20:01:34

I'd like to decrease it from 1MB to 2k

tatut20:01:21

sorry if this is in the docs and I just missed it

zane23:01:46

@U11SJ6Q0K I’m assuming you’re already aware of *print-length* and *print-level*?

tatut06:01:30

that should affect the accidental print ing but does it affect eval results?

tatut07:01:15

found cider-print-quota

tatut09:01:03

it looks like an exception with a huge ex-info payload will still get printed without truncation