Fork me on GitHub
#cider
<
2020-01-28
>
jumar07:01:10

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?

solf08:01:41

@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

jumar08:01:44

@U7S5E44DB thanks for suggestions. I haven't found anything in cider's custom vars. I'll check those links later.

FiVo13:01:26

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.

yuhan14:01:26

yeah, the "unable to resolve STATE" errors are quite opaque especially when inside macros

yuhan14:01:24

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

yuhan14:01:25

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

bozhidar17:01:26

It’s not very complex, btw. Unfortunately no one has had time for it lately.

FiVo15:01:43

yes maybe I append them to your debugger loop/recur issue