This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-06-08
Channels
- # babashka (9)
- # beginners (43)
- # biff (4)
- # calva (11)
- # cider (6)
- # clerk (1)
- # clj-kondo (4)
- # cljs-dev (6)
- # clojure (82)
- # clojure-berlin (1)
- # clojure-europe (42)
- # clojure-nl (1)
- # clojure-norway (182)
- # clojure-quebec (1)
- # clojure-uk (19)
- # clojurescript (6)
- # datahike (1)
- # emacs (30)
- # fulcro (5)
- # honeysql (6)
- # hyperfiddle (12)
- # lambdaisland (8)
- # malli (11)
- # off-topic (36)
- # pathom (26)
- # pedestal (1)
- # portal (25)
- # practicalli (1)
- # rdf (29)
- # re-frame (17)
- # reitit (1)
- # releases (1)
- # sci (37)
- # shadow-cljs (15)
- # vim (10)
- # xtdb (13)
hello, I'm having an issue in a cljs cider-repl buffer (I haven't encountered it in a clj repl): after a while, smartparens functions stop working properly: sp-kill-word will kill the word fine, but also move my cursor to the beginning of the line (before the *ns*>
"prompt") and the message "Text is read only" will show up below. I have to run cider-repl-clear-buffer
and then everything works fine again (until the problem re-appears). I'm using smartparens-strict-mode
in cider-repl buffers
I'm using doom emacs, I can't remember if I had it when I was using regular emacs
I feel like it's more of a smartparens issue than a cider issue (when buffer gets too large ?), has anyone encountered this issue ?
Using the cider repl buffer is not going to be as effecitve as using the source code buffers, especially if logs, long lines or lots of content is pushed to the repl buffer.
Perhaps there is a size limit set on the repl buffer, usually via the Cider variable, e.g. cider-repl-buffer-size-limit 100
Also suggest setting cider-repl-display-help-banner nil
to reduce the size of the repl buffer, to avoid slowdown
Note that I do not use the REPL buffer, so 100 is a very low number. I think the default is something like 1000