Fork me on GitHub
#emacs
<
2018-12-04
>
anthony-galea13:12:15

@danielcompton fyi, with this config it works for me on macOS:

(use-package super-save
  :ensure t
  :init
  (setq super-save-auto-save-when-idle t)
  :config
  (super-save-mode +1))
this is not required for it to work: (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 🙂

orestis13:12:12

super save can be extra annoying when figwheel fails to pick up some changes though. Not sure how to fix that.

macrobartfast17:12:16

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?

lilactown17:12:38

does pressing q not close the error pane?

macrobartfast17:12:05

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.

macrobartfast17:12:48

I'm guessing some of the more gui emacs provide pop up or overlays that get dismissed.

macrobartfast17:12:17

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.

macrobartfast17:12:23

I dont' want to get rid of it as I don't have it, but that's what I was seeing, apparently.

macrobartfast17:12:29

I guess what I need is an error message that creates a new pane that then can be dismissed leaving the previous pane arrangement.

macrobartfast17:12:20

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.

macrobartfast17:12:54

but my whole approach may be off.

macrobartfast17:12:34

just preventing the pointer from moving to the error buffer would probably be a good start, but not sure how to do that.

Eccentric J20:12:31

I’ve got a clj repl on the top right and a cljs repo on the bottom right

Eccentric J20:12:04

Whenever I execute a command against a cljs file like the bottom left I get a “No CLJS repls in the current session”

lispers-anonymous22:12:21

Looks like you’re using figwheel. Did you open up the webpage and allow figwheel to finish connecting before you started evaluating cljs code?

Eccentric J22:12:41

The figwheel page with the random port?

lispers-anonymous14:12:02

It would be going to a web browsers and loading up localhost on whatever port your application is hosted on.

Eccentric J18:12:52

Oh in that case yes, I was viewing the web application and figwheel has built the project.

dpsutton21:12:25

your repl says "pending-cljs" it hasn't finished the transition from clj -> cljs

macrobartfast21:12:43

what are your setups for evaluating code/seeing errors?

chris_johnson22:12:17

@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

chris_johnson22:12:19

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. 😇

Eccentric J22:12:21

It’s been saying pending-cljs indefinitely

Eccentric J23:12:06

My setup is figwheel, cider, spacemacs using a luminus web app template.

macrobartfast23:12:15

@chris_johnson that is really helpful, and (when convenient) I'd actually really appreciate any .emacs.d archaeology...

macrobartfast23:12:39

I've been in this situation for (embarrassed now!) about 2 years.