Fork me on GitHub
#spacemacs
<
2020-05-01
>
practicalli-johnny01:05:23

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)

jumar06:05:04

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?

jumar06:05:57

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

jaide17:05:06

I've been using it on my OS X Catalina Air no major problems I've noticed after updating to latest develop a day or so ago.

jaide17:05:35

One note is that tools like clj-kondo are merged into the clojure layer on develop so it's a slightly different process to enable it.

otwieracz09:05:54

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

aisamu12:05:00

Would cider-eval-sexp-at-point work for you?

otwieracz09:05:35

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

otwieracz09:05:59

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

sgepigon11:05:22

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

otwieracz11:05:07

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

☝️ 4
😭 4
aisamu12:05:00

Would cider-eval-sexp-at-point work for you?

practicalli-johnny12:05:00

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

practicalli-johnny12:05:33

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.

practicalli-johnny12:05:32

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

practicalli-johnny12:05:57

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/

otwieracz12:05:08

I will consider that.Thanks.

practicalli-johnny12:05:32

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 :)

☝️ 4
jaide21:05:53

Anyone ever encounter company-capf: Readtable JSON error 37

practicalli-johnny01:05:57

Never noticed this. Does this appear on the *messages buffer or something that Cider is showing?*

jaide02:05:50

If I type something like my-lib/, it will change it immediately to my-lib, then show that in the status.

jaide02:05:25

It is listed in the messages buffer as well but it has become an obstacle in writing working code.

practicalli-johnny12:05:39

Sounds like something is broken / corrupt with company package. If you upgraded the packages recently, then try delete company and restart Emacs. Or try delete the .elc files for company and restart Emacs. Or disable auto-completion / company until you have time to fix the problem.

jaide16:05:32

Alright I’ll give that a shot.

jaide18:05:08

Unfortunately that didn’t work

jaide19:05:14

Ooh progress! I traced it down to the related package.

jaide21:05:00

Anytime you try to write clojure?