Fork me on GitHub
#cider
<
2019-11-19
>
dromar5603:11:19

What's this yellow highlight? flycheck with clj-kondo tells me "handler/site" is deprecated, but it doesn't seem to be the one doing the highlighting

dpsutton05:11:05

It’s CIDER highlighting it. I ran across the other day and forgot about it and had the same reaction as you :)

bozhidar06:11:11

Yeah, CIDER knows what’s deprecated based on var metadata.

tomd09:11:56

Yesterday my Cider started asking me for ClojureScript REPL type everytime I jack in. I use a custom type (which does appear in the list, so no big problem) but I don't think this should matter. I tried setting cider-cljs-repl-type (globally with setq-default) but that doesn't help. Has something changed recently, or is it likely something I've done has caused this? Thanks

manuel14:11:14

Has anything with regard to CIDER + Company completion changed lately? I cannot complete some candidates. E.g. if I write (compojure.core/ and press my key binding to activate Company completion, I get No completion found. Note the Company is working fine everywhere else, meaning that if I write (compo and try to complete that I get the popup with compojure, compojure.core, and other candidates.

dpsutton14:11:29

in the repl or in source buffers?

manuel14:11:20

source buffers

manuel14:11:34

and after jack-in

dpsutton14:11:30

what's your keybinding bound to?

manuel14:11:02

company-complete

dpsutton14:11:31

try company-complete-common

dpsutton14:11:02

do you have lsp in the mix by any chance?

manuel14:11:24

nope, I'll try your suggestion

manuel14:11:57

same No completion found message with company-complete-common

manuel14:11:59

it seems to not be working only when I try to complete requires, e.g. : if I require [clojure.string :as string] and then try to complete (string/.

manuel14:11:55

ok, I am not able to reproduce it with emacs -Q. I'll debug my setup. Sorry for the noise. 🙂

dpsutton15:11:29

let us know the ultimate offender. if its common its worth knowing about if not documenting 🙂

ericnormand16:11:14

@pez I don't know the answer but I should clarify. I meant "most editors can do this, some need settings adjusted".

ericnormand16:11:28

I also know that I didn't have it turned on in Cider for years

pez17:11:25

@ericnormand so here’s the answer. 😃 It is interesting because I have tried to help my Emacs wielding colleagues to get that now and then, but we have failed every time, and concluded the feature does not exist in CIDER. Never thought it could be behind a setting. It is such an important thing from an ergonomics point of view that one of them switched to Calva because of this. Don’t know if I should tell him about the setting now… haha

dpsutton18:11:55

these are necessary for me as well

(setq cider-invert-insert-eval-p t)
  (setq cider-switch-to-repl-after-insert-p nil)

dpsutton18:11:09

for using the insert into repl commands. automatically eval and don't move point to the repl

dpsutton18:11:18

huge quality of life improvement for me

dpsutton18:11:51

also these

:bind (:map
         cider-repl-mode-map
         ("RET" . cider-repl-newline-and-indent)
         ("C-j" . cider-repl-return)
         :map
         paredit-mode-map
         ("C-j" . cider-repl-return))

dpsutton18:11:08

making enter in the repl give a newline and control-j send it.

fappy22:11:58

Hi everyone! After we’ve dropped into the CIDER debugger, if we happen to move to some other buffer etc and want to jump back to where the debugger is, is there a keystroke or function for doing that jump? And is there some way to see whether we’re still in the debugger vs the code is now continuing to run normally?