when running cider-read-and-eval-defun-at-point on

(defn foobar [x]
  (* 2 x))

Show: Project-Only All
  Hide: Clojure Java REPL Tooling Duplicates  (24 frames hidden)

2. Unhandled clojure.lang.Compiler$CompilerException
   Error compiling *cider-repl past/someproject:localhost:3333(clj)* at (1:1)
   #:clojure.error{:phase :compile-syntax-check,
                   :line 1,
                   :column 1,
                   :source
                   "*cider-repl past/someproject:localhost:3333(clj)*"}
1. Caused by java.lang.RuntimeException
   Unable to resolve symbol: foobar in this context

                 Util.java:  221  clojure.lang.Util/runtimeException
                  core.clj: 3214  clojure.core/eval
                  core.clj: 3210  clojure.core/eval
                  main.clj:  437  clojure.main/repl/read-eval-print/fn
                  main.clj:  458  clojure.main/repl/fn
                  main.clj:  368  clojure.main/repl
               RestFn.java: 1523  clojure.lang.RestFn/invoke
                  AFn.java:   22  clojure.lang.AFn/run
                  AFn.java:   22  clojure.lang.AFn/run
               Thread.java:  748  java.lang.Thread/run

cider-eval-defun-at-point works fine, however.

to define the function in the buffer, that is.

This is a cljs file in a Reagent project, by the way, running in a browser.

@U0X9N9ZK5 what about using comment forms?

Well, I have in the past… but that just clutters my code overall and makes it less readable… and I have to type it all out. When cider-read-and-eval-defun-at-point worked, it was literally just a matter of the binding that triggered the function, tap in a couple arguments when it appeared in the minibuffer, and enter and voila.

Right, that's understandable - I've never used that command before but it seems useful. What I sometimes do is take advantage of the fact that (#'foo x) calls the function in the var - so I'll do a quick wrap-round and forward-sexp

((defn foobar [x]
   (* 2 x)) 10)

(this is particularly useful when you're debugging some function definition on a fixed set of arguments - cider-eval-defun from anywhere in the form re-defs the function and calls it in one go)

That is really interesting… I’ll give those approaches a try.

do you use something to toss the wrap-around on and remove it quickly?

I know there are things in Emacs that do that, but I do it semi-manually with paredit.

I use lispy(ville) but paredit or any other structural-editing package should work fine once you get it into muscle memory 🙂

for me it's ESC (evil normal state), { (start of defun) M-9 (wrap in parens) M-a (goto end of form and enter evil insert state) then at the end, navigate to the right spot and M-r to raise

@UCPS050BV thanks!