mb a zoom or otherwise? would be tremendously helpful in developing my own workflow

This is the foundation of my workflow with Emacs & Cider (the key bindings may be Spacemacs specific but all the Clojure commands are cider) https://youtu.be/NDrpclY54E0

I am using Portal more than the Cider inspector when visualising data in different ways (automatically capturing all evaluation results and logs for a complete repl history) https://practical.li/clojure/data-inspector/portal/

I'll extend that foundation workflow with some reloading tools / component state libraries, especially for server-side (backend) work, e.g building api's and similar services. Although that workflow is not specific to Emacs and I also use it with Neovim & Conjure (or any Clojure nrepl supported editor) https://practical.li/clojure/clojure-cli/repl-reloaded/

thank you @U05254DQM !

@U6D1FU8F2 http://www.parens-of-the-dead.com might also be of interest 🙂

I'm happy to give a demo if you'd like, feel free to DM

@U07FCNURX been a fan for many, many years ❤️

What cider-nrepl are you using? Are you using cider-connect or cider-jack-in?

cider-jack-in

[nREPL] Starting server via /usr/local/bin/clojure -A:dev -Sdeps \{\:deps\ \{nrepl/nrepl\ \{\:mvn/version\ \"1.0.0\"\}\ cider/cider-nrepl\ \{\:mvn/version\ \"0.44.0\"\}\}\ \:aliases\ \{\:cider/nrepl\ \{\:main-opts\ \[\"-m\"\ \"nrepl.cmdline\"\ \"--middleware\"\ \"\[cider.nrepl/cider-middleware\]\"\]\}\}\} -M:cider/nrepl

Thanks! You aren't using clojure-storm, correct?

nope

I'm not expecting slowness in that case, if you'd like to contribute fixing it, you can create a standalone cider-nrepl server, and hit Ctrl \ there, which will create a thread dump that you can share over a github issue

As for the compilation-error aspect, it changed, please see https://docs.cider.mx/cider/usage/dealing_with_errors.html > Starting from CIDER 1.8.0, only runtime exceptions (and not compilation errors) will cause a stacktrace buffer to be shown [...] This can be customized away but I don't believe it will fix any slowness - we'd better appreciate a thread dump

(that is, when the slowness happens)

it always happens on every error, i think the middleware is doing a lot of extra work parsing the stacktrace and it never communicates back to emacs? I am not sure. I expect that when errors happen I can quickly get an exception buffer to navigate stack trace. BTW I set the new variable "cider-clojure-compilation-error-phases" to nil and the same problem. So what do you mean by create a standalone cider-nrepl server and hit Ctrl \?

> it always happens on every error, i think the middleware is doing a lot of extra work parsing the stacktrace and it never communicates back to emacs? Yes but it could be anything, the thread dump would help it also would be very helpful to determine whether this is project specific (sometimes specific dependencies can create unforeseen scenarios) > So what do you mean by create a standalone cider-nrepl server and hit Ctrl \? https://docs.cider.mx/cider/basics/up_and_running.html#connect-to-a-running-nrepl-server Create a repl that has cider-nrepl in it, and cider-connect to it Beforehand, set Elisp nrepl-log-messages to t, this will enable a nrepl-log buffer So an accurate report would ideally include: • the thread dump (https://chat.openai.com/share/b5269b9a-4f3c-430f-a843-84698d216c28) • the nrepl-log • whether this happens in a minimal project Thanks a lot, and happy new year!

I've been using this for over a decade and never had this happen all of a sudden

I appreciate that, but CIDER is a living project, we move things forward from time to time

No one else has experienced this?

Not with your exact combination of factors (cider-nrepl latest which fixed many things, enrich-classpath disabled, no clojure-storm which also interfered in a past version)

Oh you mean take a thread dump outside of emacs

?

Yes, to the JVM process, from iterm or such

Ah okay, like basically, run the command as if it were jacking in and then do it

Spawn cider-nrepl from iterm, cider-connect, (hopefully) reproduce the slowness in emacs, hit Ctrl \ in iterm right then. It will print a dump over iterm. Thanks!

aha thats what you mean

thanks

Created https://github.com/clojure-emacs/orchard/issues/222 out of our DMs - I'm hoping that would be a root cause fix

Thanks! (This excessive slowness I experienced may have been indirectly caused by modding Baldurs Gate 3... Which if anyone has heard of, is gigantic. Especially when you have decompiled all of the scripts and metadata for every asset.)