Fork me on GitHub
#cider
<
2020-01-19
>
borkdude11:01:54

I'm getting stdin isn't a terminal when doing projectile-replace. I didn't get this before, not sure what's wrong ... any hints?

borkdude11:01:17

ah, I found it. it's related to stty icrnl which I have in my zsh config

borkdude11:01:07

is there a way to use projectile-replace on only .cljc files in my project and ignore all other files?

bozhidar22:01:02

Nope. It goes over all files in a project, although it should be hard to add some filtering by filetype/filename.

rschmukler18:01:56

Hey all! I'm running into an issue where cider-apropos seems to be freezing my emacs. This only happens when using JDK 13 and 14 preview... JDK 8 seems to work fine. Any tips on how I could troubleshoot this?

rschmukler19:01:28

Hmmm looks like it's no longer working with JDK 8 either - but I think switching the JDK caused it to break in the first place - although I'm not 100% sure of that

rschmukler19:01:14

Further investigation reveals that if I call cider.nrepl.middleware.apropos/apropos from my nrepl process it returns matches / works as expected

rschmukler19:01:21

Looks like it's a helm cider issue...

ahungry20:01:01

hey all - is there any cider functionality similar to "Invoke defn at point" (where it would perhaps prompt for input for the arguments)? I find I'll often redefine/work on a function and want to execute it - this requires switching to that NS in the REPL, and then retyping to call it

ahungry20:01:50

Maybe the closest workflow based thing is to wrap in a (comment and C-c C-v C-v

ahungry20:01:39

ok, it was simple to implement

ahungry20:01:45

(defun my-cider-tinker ()
         (interactive)
         (let ((eval-result (call-interactively #'cider-eval-defun-at-point)))
           (cider-interactive-eval
            (format  "(@*1 %s)" (read-string "args: ")))
           ))

ahungry20:01:13

although it doesn't display the nice overlay inline like the standard C-c C-c does...guess I'll have to tinker with that

dpsutton20:01:53

your read-string will not be able to handle most clojure literals

ahungry20:01:59

What ones do you think it may fail on? I've tested with various literals, numbers, quoted strings, vectors, maps

dpsutton20:01:43

I think a #_(my-fun foo bar) right above the function is what i would do. i thought read-string would choke on maps and sets but i guess not

ahungry20:01:32

I saw a #dbg reference in another cider-eval internal - is that something specific to cider? the hash<some form> syntax?

ahungry20:01:45

not the syntax, but the macro expansion / meaning behind it