This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # adventofcode (100)
- # announcements (7)
- # architecture (1)
- # aws (14)
- # beginners (209)
- # calva (30)
- # cider (5)
- # cljdoc (2)
- # cljs-dev (37)
- # cljsrn (2)
- # clojure (133)
- # clojure-dev (20)
- # clojure-finland (1)
- # clojure-italy (10)
- # clojure-nl (19)
- # clojure-spec (56)
- # clojure-uk (49)
- # clojurescript (57)
- # clojurex (8)
- # core-async (2)
- # core-logic (1)
- # cursive (38)
- # data-science (19)
- # datomic (28)
- # devcards (3)
- # duct (8)
- # emacs (28)
- # figwheel (1)
- # figwheel-main (31)
- # fulcro (2)
- # jobs (1)
- # kaocha (1)
- # klipse (2)
- # mount (6)
- # nrepl (43)
- # off-topic (20)
- # pathom (3)
- # pedestal (1)
- # re-frame (15)
- # ring-swagger (1)
- # shadow-cljs (47)
- # spacemacs (19)
- # sql (20)
- # tools-deps (58)
- # unrepl (13)
- # vim (5)
@danielcompton fyi, with this config it works for me on macOS:
this is not required for it to work:
(use-package super-save :ensure t :init (setq super-save-auto-save-when-idle t) :config (super-save-mode +1))
(super-save-auto-save-when-idle t)but will save after 5 seconds when emacs is idle: https://github.com/bbatsov/super-save/blob/62512f60d6685d8601e2021d95e77603b6d96885/super-save.el#L61 funny never noticed that dot until now 🙂
super save can be extra annoying when figwheel fails to pick up some changes though. Not sure how to fix that.
I use emacs/cider in a terminal; when I have an error it appears in a new pane that gains focus; I have to navigate back to my file to resolve the error; if there are two files open I have to explicitly navigate back to the file the error pane replaced; can I set things up to handle the display/notification of error less obtrusively?
it does, but if I had two panes side by side previously (when working with two or more buffers, which I usually am) it closes them too.
I'm guessing some of the more gui emacs provide pop up or overlays that get dismissed.
as a side note, I saw a setup recently that seemed to show a large yellow caution sign that appeared over everything for a second... not sure what was causing that to appear.
I dont' want to get rid of it as I don't have it, but that's what I was seeing, apparently.
I guess what I need is an error message that creates a new pane that then can be dismissed leaving the previous pane arrangement.
right now it uses an open pane, and so I have to dismiss the pane entirely, or awkwardly navigate back to the previous file before switching to my main work buffer to resolve the issue.
just preventing the pointer from moving to the error buffer would probably be a good start, but not sure how to do that.
Whenever I execute a command against a cljs file like the bottom left I get a “No CLJS repls in the current session”
Looks like you’re using figwheel. Did you open up the webpage and allow figwheel to finish connecting before you started evaluating cljs code?
It would be going to a web browsers and loading up localhost on whatever port your application is hosted on.
Oh in that case yes, I was viewing the web application and figwheel has built the project.
@macrobartfast I use cider and emacs (currently in OSX “GUI” emacs but fullscreen with no menubar, previously in terminal) and for me the cider-error stacktrace window is displayed over the “other window” (e.g. if I
C-c C-e in my editor, the
cider-error buffer is displayed in my REPL window), but pressing
q simply dismisses that buffer and returns me to my regularly-scheduled REPL buffer
Not sure what config difference would lead to that different behavior but what you describe is tooth-grindingly poor quality of life. If digging through my
.emacs.d can help you not have that, I’m happy to do it. 😇
@chris_johnson that is really helpful, and (when convenient) I'd actually really appreciate any .emacs.d archaeology...