Fork me on GitHub
#emacs
<
2018-10-17
>
dpsutton01:10:39

@jr0cket that's the setup I use. I can't imagine going back.

dpsutton01:10:12

If it eagerly evaluates it makes it feel limited to only trivial calculations

practicalli-john01:10:31

@andy.fingerhut sorry, I should have been clearer. If the default key binding in a REPL buffer for evaluating an expression was changed to C-RET, how many people would this annoy, anger or confuse. I don’t use the REPL buffer myself, hence the question. It seems Dan and I make two votes for such a change, so 2-0 so far.

practicalli-john01:10:19

I use the code buffer pretty much exclusively, unless I debug with printing. I’ve long been doing the journaling of the design choices (I call them REPL experiments) that Stuart talks about in the running with scissor talk.

practicalli-john01:10:15

However, the REPL and REPL history experience seems to be broken in Spacemacs (Evil state). While looking into that I noticed the REPL buffer didn’t do multi-line. Every other editor and even the Clojure CLI tools with rebel.readline does multi-line, so this behaviour now seems to be the norm.

dpsutton02:10:20

i think rebel readline does multiline by unfinished parens. I don't much like this approach but I think @richiardiandrea built a clever feature that will auto close all parens and eval if that's the way you like to work

richiardiandrea03:10:36

Well not even mine, but I think I would be able to dig it up from my emacs conf 😃

dpsutton03:10:48

I thought you committed that to cider

richiardiandrea04:10:35

Uhm if I did that I do not remember 😄

bozhidar08:10:14

I always code in a source buffer and just send stuff for evaluation to the REPL. From time to time I might do some experiments in the REPL itself, but that happens pretty infrequently.

bozhidar08:10:25

I did a (bad) demo of my approach a while ago https://www.youtube.com/watch?v=aYA4AAjLfT0

👍 4
bozhidar08:10:48

> However, the REPL and REPL history experience seems to be broken in Spacemacs (Evil state). While looking into that I noticed the REPL buffer didn’t do multi-line. Every other editor and even the Clojure CLI tools with rebel.readline does multi-line, so this behaviour now seems to be the norm.

bozhidar09:10:50

@jr0cket not sure what you mean by this. CIDER’s REPL does multi-line just like any other Emacs REPL (using unfinished expression or C-j) and that’s properly reflected in the history.

practicalli-john11:10:11

@bozhidar its Spacemacs Evil specific and I've been thinking about how to improve this in the Spacemacs clojure layer config. C-j is used for traversing history so cant be used for insert-and-indent in the REPL buffer and the REPL buffer keybindings only works in Evil insert or Emacs state

jumar11:10:45

I use evil mode and find C-j behavior perfectly acceptable. Not sure what you're talking about.

practicalli-john12:10:48

Yes but the C-j is for traversing REPL buffer history in Spacemacs Clojure layer, not for cider-repl-newline-and-indent. In the Cider docs it defines C-j as the keybinding for newline interaction in the repl, but the repl history in Spacemacs over-rides this. https://cider.readthedocs.io/en/latest/using_the_repl/#customizing-newline-interaction

llsouder17:10:44

I have [cider/piggieback "0.3.9"] in my project.clj but emacs give me an error that it is missing cemerick piggieback. I have search my project, .lein and .emacs for a reference to cemerick and cannot find one. I also did a lein deps :tree

dpsutton17:10:15

What version of cider are you running

llsouder18:10:06

How do I control the version of cider? I just checked out my spacemacs config SPC f e d and I dont see any version numbers.

dpsutton18:10:44

so that was in the transition period of cider towards cider/piggieback from cemerick/piggieback. and that may predate cider/piggieback so it doesn't know that that is an acceptable solution

dpsutton18:10:05

let me check out 0.17 and see if there's a knob. i think there'sa defcustom somewhere to inhibit those checks. just need t osee what the name is

dpsutton18:10:03

you can monkey patch it here (defun cider-verify-piggieback-is-present ()) with that

dpsutton18:10:36

and you can find that function and see how it is checking for the presence of piggieback

bozhidar18:10:33

Yeah, that seems like a reasonable approach

bozhidar18:10:03

In 0.19 I’ll completely drop the cemerick/piggieback stuff, so we can simplify a bit the code.

llsouder18:10:23

M-x configuration-layer/update-packages
154 packages to update 😛

dpsutton18:10:28

ha. i did 127 or so a few weeks ago and it worked flawlessly. good luck

llsouder18:10:38

when I start the repl I see emacs using 0.19 snapshot but my repl says 0.18 snapshot?

llsouder18:10:22

beside that I still get the error after I start figwheel and use (cljs-repl)

llsouder18:10:21

I guess the dependency is in figwheel?

dpsutton19:10:26

oh you're getting this from figwheel, not cider

dpsutton19:10:36

which version of figwheel are you on. i think you need to be on 16+

llsouder21:10:02

I put back the cemerick version. I am using 0.5.16 of figwheel

llsouder21:10:41

I posted my real problem in #figwheel , all day I have been fidgeting with the settings, starting fresh, updating things, following tutorials. Not really how I wanted to spend my home coding time.

llsouder21:10:48

I think what it comes down to is the emacs repl is not calling mount-root when I save a file but lein figwheel does.

llsouder21:10:40

ok, figwheel updates my page from emacs when I use inf-clojure but then there is no cider so I dont get the cool evaluations.

dadair21:10:53

Trying to resolve an annoyance that I’ve let go on for too long. Whenever I type the following on a new line:

(def some-var "some-string")
when I type the first character of “some-string” (after the opening double quote), the form always gets indented for some reason:
(def something "some-string")
^did not type
I assume it has something to do with “some-string” being ambiguously parsed as the docstring, but I’m not sure why it is indenting (or what is indenting it automatically). Any advice on debugging/changing? Anyone else running into this?

dadair21:10:11

Active modes: clojure, clojure-refactor, cider, EditorConfig, paredit