Clojurians Log v2
cider
Hello Folks,
I just got a new desktop Mac, and the vastly improved memory made me wondering: what ways are there to tune my cider dev set up.
I normally do cider-jack-in-clj&cljs which runs my clojure and shadow-cljs stuff in my mono repo for my web app.
But would it speed things up if I for instance use different Xmx settings?
What is the route. I asked chatGPT, but the result was a bit hallucinating afaict
try tuning smth like cider-clojure-cli-parameters, cider-shadow-cljs-parameters etc
If we talk about an empty project or a project that doesn't keep much data in memory, than raising the heap above 1-2GB wouldn't do anything.
By default, if you don't specify heap size explicitly, JVM starts with the maximum heap equal to 25% of total system memory. So it's probably already 4-8GB on your system by default
Ah yeah it is indeed... 8gb now The code base is fairly sizeable at the moment, so it's by no means a new project. Once everything is started it's fairly snappy, but hot reloading didnt speed up that much compared to my macbook air, which made me wonder if i was missing something
I want to enable Javadoc parsing for CIDER. The https://docs.cider.mx/cider/config/basic_config.html#use-enrich-classpath point me towards setting cider-enrich-classpath to t, but within Emacs itself, describe-variable indicates that this variable is obsolete.
cider-enrich-classpath is a variable defined in 'cider.el'.
Its value is nil
This variable is obsolete since 1.19.0.
Removed.
Yeah, exactly.
We hadn't redeployed the docs for the dev branch. I'll do this now.
Yes, what you see is the parsed Javadoc processed by CIDER. I can't say why it doesn't show the full doc though, I don't have deep internal knowledge about the parser we use.
I see this was actually addressed in a https://clojurians.slack.com/archives/C0617A8PQ/p1746087425042759 - I will try that instead!
I believe I have parsing enabled with the new cider-download-java-sources feature.
I have a follow up question. This is what I should expect to see if javadoc parsing is enabled, right? This parser appears to parse only a subset of the Javadoc-style comments that produce the full documentation page.