This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-01-28
Channels
- # babashka (28)
- # beginners (252)
- # bristol-clojurians (2)
- # calva (28)
- # cider (11)
- # clj-kondo (15)
- # cljs-dev (7)
- # clojure (378)
- # clojure-europe (4)
- # clojure-italy (4)
- # clojure-nl (3)
- # clojure-norway (4)
- # clojure-uk (32)
- # clojurescript (128)
- # cursive (39)
- # data-science (18)
- # docker (37)
- # figwheel-main (10)
- # fulcro (45)
- # ghostwheel (7)
- # graalvm (2)
- # hugsql (1)
- # jobs (2)
- # joker (5)
- # kaocha (5)
- # luminus (12)
- # off-topic (37)
- # onyx (4)
- # pathom (22)
- # pedestal (70)
- # re-frame (7)
- # reagent (30)
- # ring (4)
- # shadow-cljs (12)
- # spacemacs (1)
- # sql (26)
- # tools-deps (7)
- # vrac (2)
- # vscode (7)
- # xtdb (27)
This might be a more general emacs question but I often found cider opens a new window (such as repl window, inspector window, etc.) at the bottom; but I'd like to open it at right. is there a way to enforce that?
@jumar You can check all cider customizations using M-x customize-group cider
, but if I remember correctly there weren't options for that. Now, as a more general emacs answer, the way to configure emacs to open windows the way you wants is through modifying buffer-display-alist
[1]. There are also packages that help you achieve that such as shackle [2]
[1] https://www.gnu.org/software/emacs/manual/html_node/elisp/Displaying-Buffers.html
[2] https://github.com/wasamasa/shackle
@U7S5E44DB thanks for suggestions. I haven't found anything in cider's custom vars. I'll check those links later.
https://github.com/bmag/emacs-purpose might be useful too
I also sometimes have trouble understanding the debugger. For example the following won't even compile:
(defn test2 []
(loop [i 0]
#dbg ^{:break/when (= i 7)}
(when (< i 10)
(println i)
(recur (inc i)))))
whereas the following works fine
(defn test2 []
(loop [i 0]
(when (< i 10)
#dbg ^{:break/when (= i 7)}
(println i)
(recur (inc i)))))
when replacing the #dbg...
with a simple #break
in the first function example, I can compile, but am not dropped in the debugger.yeah, the "unable to resolve STATE" errors are quite opaque especially when inside macros
I think it conflicts especially with forms involving recur
, usually I try moving the #dbg tag around to see if it compiles or resort to another method of debugging like scope-capture
maybe you could open an issue on Github, I've opened a few relating to the debugger but it seems to be quite a complex and not well-understood part of the codebase
There’s even a bit of high level documentation https://docs.cider.mx/cider/debugging/debugger.html#_debugger_internals