This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # announcements (4)
- # beginners (82)
- # boot (1)
- # calva (26)
- # cider (13)
- # clj-kondo (41)
- # cljs-dev (25)
- # cljsrn (7)
- # clojure (85)
- # clojure-berlin (1)
- # clojure-brasil (1)
- # clojure-dev (13)
- # clojure-europe (11)
- # clojure-italy (27)
- # clojure-nl (8)
- # clojure-russia (6)
- # clojure-spec (32)
- # clojure-uk (15)
- # clojurescript (61)
- # core-async (1)
- # cursive (9)
- # data-science (1)
- # datomic (18)
- # duct (1)
- # emacs (2)
- # events (7)
- # fulcro (13)
- # graalvm (5)
- # immutant (1)
- # jobs-discuss (63)
- # leiningen (3)
- # off-topic (48)
- # om (3)
- # pathom (13)
- # planck (20)
- # prelude (2)
- # re-frame (55)
- # reagent (13)
- # reitit (5)
- # rewrite-clj (12)
- # shadow-cljs (67)
- # spacemacs (14)
- # sql (5)
- # tools-deps (4)
- # vim (23)
- # yada (2)
This with that the repl window has problems with large data structures is pretty bad. I am not sure where it bogs down, but I suspect it is in the lexing and building up of the model.
@pez/@lspector Cider has had problems with “large” values in the repl window as well.
Don’t remember if it’s a problem pasting large values, but it has deffo been a problem when you have large values returned from nrepl.
Oh, there can be some stuff in future nrepls which helps with this https://github.com/nrepl/nrepl/pull/106
Thanks, @slipset! I added an issue for this now, and included that nrepl PR as a clue to solving this: https://github.com/BetterThanTomorrow/calva/issues/228
This actually makes me doubt the decision to go with the Webview, writing a new Clojure editor... It is such a big thing to take on. We should investigate how far we could take things using a regular editor window instead. It would bring other problems, but so much of the fundamentals of Clojure editing is already solved by VS Code and Calva... Hmmm... Anyway, it is not something I can or should jump to right now. Just something to keep considering.
@lspector , this is on another Mac i sometimes use. Funny that Apple seem so undecided on what it should be called.
Also, evaluate to repl window now uses
ctrl+alt modifier instead of just
alt, so you shouldn't run into troubles with that dead key any more.
I have a question regarding the REPL window. Nested changes only seem to be imported when I do
(use 'user :reload-all) whereas I'm used to do
(use 'user :reload) when not in the REPL window. Is this a bug or am I missing something?
And are there any best practices for debugging? Like showing the stack trace? I can only see a part of that in the task-console-window that launched the REPL server but all the important frames aren't shown but hidden in the
... 39 more ... line at the end of the trace. In the REPL window
*e is bound to the last exception that occured in that window and not the one that is shown in the task window.
Is there a way to 'evalCurrentFormInREPLWindow' without the cursor jumping into the REPL?
From a server. But I just recognized that those might get logged to that window because of logger settings. Maybe, I'm able to redirect them somehow. But it'd still be nice to know if there are some kind of best practices for debugging with calva
@pez The output window works like that but doesn't have any colours or pretty print like the Calva repl.
@pez also I like to eval each expr at a time. With the cursor jumping between windows I have to keep switching between the two.
@linkerfelix if you do find some log settings that work better for you, please create a wiki page for debugging and write some tips there.
@pez I will have a look 🙂 Do you have some comments on the
:reload-all subject? :relaxed:
I am not quite following that question, @linkerfelix. Have you tried the Calva refresh commands?