Clojurians Log v2

I assume it's either CIDER or the newish changes to error messages in Clojure 1.10.1 onwards. Maybe a screenshot would be useful (I rarely look at error messages that closely)

What's the difference between master and develop branch and when we can reasonably expect a new release to catch up on changes in develop?

Should I expect any issues when using develop with Emacs 25.3.1 on Mac OS X Catalina?

evil-users, how do you eval single sexp fron normal-mode?

Because any eval-last-sexp command in normal mode requires you to move one character after the sexp.

And if there’s nothing in the line other than this sexp - I end up having to go into insert-mode only to evaluate.

@slawek098 There’s spacemacs/cider-eval-sexp-end-of-line which is bound to SPC m e l or SPC m e $ on develop

Oh, I haven’t written. There’s evil-move-beyond-eol

@slawek098 rather than complext your evil setup, you can always move to the line below to eval a previous expression. There is no need to change the behavior of Evil or add complexity to the Evil setup by moving beyond a boundary.

I mainly use cider-eval-defun-at-point which will evaluate the whole current expression, regardless of where the cursor is. I consider this the default evaluation command.

I only use cider-eval-last-sexp when I explicitly want to evaluate a nested function

There are several more ways to evaluate an expression, so no need to stick with just last-sexp https://practicalli.github.io/spacemacs/evaluating-clojure/

I will consider that.Thanks.

This is Emacs though, so you can of course do what works best for you as long as you are happy to maintain your own custom changes :)

Anyone ever encounter company-capf: Readtable JSON error 37

Anytime you try to write clojure?