M-p

M-p and M-n are bounded to cider-repl-previous-input and cider-repl-next-input

Ah! Fantastic

and M-r if you want to search through your previous input 🙂

Are you talking about eldoc? https://docs.cider.mx/cider/config/eldoc.html#displaying-eldoc-for-the-symbol-at-point

talking about this popups

Would love to control this myself

You could try following that instruction (`(setq cider-eldoc-display-for-symbol-at-point nil)`) to see if it gets disabled

still there

is also kind of buggy, doesn't always display

ok, please (setq nrepl-log-messages t) , cause the popup to show up again, visit the *nrepl-messages [...] buffer, see what request/response cycle is including all that info requests are marked by --> and have an id and op responses are marked by <-- and have an id (matching the request) and the response data then you'd have to grep in the cider package which defuns are calling that op

(Slightly excessive work if it's the first time doing it, but it's a super useful technique)

looks like something that is requesting a info

Yep, that's what I would have guessed :) Info is obtained via cider-sync-request:info , mainly

but not for every popup, just for the ones that shows a docstring

there's defcustom cider-use-tooltips t , responsible for defun cider--help-echo which uses info hope that's it!

nice! cider-use-tooltips`` did the trick!

thanks!

it would be nice to have a way of tracking those down. I can track most things down in emacs but no idea about those

one way is as shown above, starting by the nrepl log and following that trace of ops and then code another is M-x describe-key . Sometimes it works with mouse stuff

btw, we recently added Cider Storm to the docs (soon to be online) https://github.com/clojure-emacs/cider/pull/3425 Kudos for your work!

ok I found a way of tracking those, you add a breakpoint to emacs tooltip-show and can edebug them

> btw, we recently added Cider Storm to the docs (soon to be online) nice!!

> ok I found a way of tracking those, you add a breakpoint to emacs tooltip-show and can edebug them meh, false alarm. Edebug activates and you can step, but running e (backtrace) doesn't provide any useful info

a timer ends up firing the tooltip-show

anyways, thanks @U45T93RA6!