cider 2022-08-02 | Slack Archive

jumar10:08:43

I'm not sure what happened but cider-pprint-* commands no longer work for me. They simply print everything on the same line - the same result when I pprint in a comment or in a separate buffer.

(cider--version)
"1.5.0-snapshot (package: 20220628.551)"

I use spacemacs if it matters.

jumar10:08:58

just updated cider package but still the same:

Version: 20220731.522

jumar10:08:10

Another minor problem with pprint functions printing to a comment I noticed a long time ago: unlike cider-eval-defun-to-comment, cider-pprint-eval-defun-to-comment will consume the next line; that means it should be an empty line, because otherwise it simply prepends the evaluation result to the stuff on the next line which means it's commented out. Example: This

(comment
  (map inc (range 10))
  .)

is Ok with cider-eval-defun-to-comment

(comment
  (map inc (range 10))
;; => (1 2 3 4 5 6 7 8 9 10)
  .)

but is not with cider-pprint-eval-defun-to-comment

(comment
  (map inc (range 10))
  ;; => (1 2 3 4 5 6 7 8 9 10).)

bozhidar11:08:08

I can't think of any recent changes that would have affected them.

jumar16:08:59

Pprinting in general definitely worked for me not that long ago. The odd behavior of Pprint to the comment may have been there for a very long time

bozhidar10:08:53

Ah, I missed this part. Might be best to file a ticket then. Admittedly I've never used this functionality much myself.

2022-08-02

Channels