Reading https://docs.cider.mx/cider/1.1/usage/pretty_printing.html it is unclear to me if I should expect (setq cider-print-fn "") to work with the latest cider. I attempted to use this setting and it appears to not work, as pr is still being used.

that documentation lists possible values for cider-print-fn. The empty string is not one of them so I’m not sure what you are trying to do

My apologies, my speech-to-text failed there. Setting it to any value listed on that page does not appear to work.

Setting it to an invalid value does not throw an error either.

ah ok. i’d file a bug report then. And probably the easiest way to confirm and demonstration the it does not work would be with the custom version. Because there is a custom var version, i’m not sure how we could really define an invalid value

but a minimal repro in a ticket with a custom printer

(defn custom-printer [value writer options] (.println writer ^String "custom value"))

(as it can be hard to distinguish between if fipp or pprint are actually working

Hmm, interesting. (setq cider-print-fn 'true) does throw an error when attempting to pprint.

Ok, I'll mess with this more. I just wanted a quick sanity check to set my expectations.

what about (setq cider-print-fn "true"). that might just be a type error on string vs symbol

and then the string is just ignored when it actually matters

"true" succeeds in printing

I would expect that to fail

hmm, default value is "pprint", and it's not using pprint by default. Docs say it should be using what's bound to nrepl.middleware.print/*print-fn*, which is pr by default.

for sure a bug report then