Why stderr instead of stdout

[piranha]

Hi James! I wonder what's the reason behind changing the default output to stderr. 😁 Because in result I now have to pepper alter-var-root like that in every project I touch to make hashp usable with CIDER. :-)

Maybe you have better ideas of how to make it less awkward, some CIDER config maybe?

EDIT: late thought: maybe the reason is not stderr vs stdout, but an early bind to *err* makes it output to something different rather than what CIDER provides as an *err*?

[sg-qwt]

I can also confirm hashp has issue with CIDER. I cannot see hashp output in nrepl buffer when put below into user.clj

(require 'hashp.install)
(hashp.install/install :writer *out*)

Perhaps this is a CIDER bug maybe due to CIDER mess up err/out on startup?

[weavejester]

Can you give some more details on your setup? What command are you using to access nREPL, how are you loading in user.clj, etc.?

[sg-qwt]

with a dev alias in deps.edn

  :dev {:extra-paths ["dev"]
        :extra-deps {nrepl/nrepl {:mvn/version "1.5.1"}
                     cider/cider-nrepl {:mvn/version "0.58.0"}
                     dev.weavejester/hashp {:mvn/version "0.5.1"}
                     
}
        :main-opts ["--main" "nrepl.cmdline"
                    "--middleware" "[cider.nrepl/cider-middleware]"]}

put install code in dev/user.clj

(require 'hashp.install)
(hashp.install/install :writer *out*)

start with clojure -M:dev in a console then do cider-jack-in to the nrepl

No matter I install it to out or err, the hashp output is always in the console but not showing up in CIDER nrepl buffer.

@piranha 's fork ( net.solovyov/hashp {:mvn/version "0.4.0-1"}) with some out hack works for me btw.

[weavejester]

Thanks. My guess is that CIDER is redefining *out* after hashp is installed, so maybe the best solution is to allow :err and :out to be specified as the writer, and these keywords will be dynamically replaced with the associated writers at runtime.