Fork me on GitHub
#cider
<
2018-10-01
>
Arthur08:10:24

Hello guys!! a quick question: is there some kind of a "backward" command in CIDER INSPECT?? MANY THANKS!!!

agile_geek09:10:39

If you mean 'go back up one level' when you've 'drilled into' a specific data structure? I think l does that (that's the letter L but lowercase)

Arthur09:10:47

could you tell me the name of that command please? I use spacemacs with vim keybindnings for navigating, so " l " means just move one char right in my case((

Arthur09:10:38

OH!!! no!! in my case L actually does this!! Thank you a lot!!!!

blak3mill3r07:10:09

For posterity: it's cider-inspector-pop

pauld17:10:46

Does anyone else not see "clojure-toplevel-inside-comment-form" available in clojure mode?

pauld17:10:17

I'm using spacemacs, so maybe it's another spacemacs issue, but I can't seem to find this function.

pauld17:10:15

clojure-mode 20180925.330 and CIDER 0.18.1snapshot and nREPL 0.4.5 and emacs 25 are installed

bozhidar17:10:07

I certainly see it.

pauld17:10:53

ok my emacs foo is poor. It's a defcustom?

pauld17:10:11

Does that mean I need to enable it?

pauld17:10:35

Ah, seems that way. Trying now.

bozhidar17:10:07

Yeah, it’s a defcustom.

pauld17:10:53

Ok, got it working.

bbrinck20:10:04

I’m running into an issue with Cider 0.18.0 where I execute cider-eval-region or cider-eval-last-sexp but instead of just executing that code, it appears (from output of *Messages*) that the entire namespace is being evaled each time, which times out and gives an error. From my search on cider issues, it seems like there was a change to how REPL connections work recently - is there a way to debug what’s happening in this connection? Or maybe I need to change my workflow somehow?

bbrinck20:10:00

Hmm, I just manually ran cider-eval-buffer and now cider-eval-last-sexp seems to work again. This could totally be a coincidence