cider
                                
                                 cider copied to clipboard
                                
                                    cider copied to clipboard
                            
                            
                            
                        The Clojure Interactive Development Environment that Rocks for Emacs
## Expected behavior Hovering the mouse over function names in clojure buffers will display tooltips when `cider-use-tooltips` and `tooltip-mode` is on. ## Actual behavior No tooltips ## Steps to reproduce...
## Actual behavior Evaluating the following with the cursor on the last paren returns: ``` ;; cider-eval-last-sexp result (inc (inc 0)) ;; => 2 ^ ``` Pretty printing it with...
## Expected behavior `package-get-version` was recently used in `CIDER` to simplify the logic to retrieve the current CIDER version. It should return the CIDER package version as set in the...
Hello, Seems like `tap>` and the inspector can work very well together, and adding such capability takes only a few lines of code. I propose a new interactive function `cider-inspect-tap`...
When I cider-jack-in in Cider within a buffer that has no associated file or buffer, it starts a nrepl, but it seems nrepl is trying to create a .nrepl-port file...
## Expected behavior Given this .dir-locals file ``` (clojurescript-mode . ((cider-clojure-cli-aliases . "-A:fig") (cider-default-cljs-repl . figwheel-main)) ) ``` And this deps file ``` { .... :aliases { :fig {:extra-deps {com.bhauman/figwheel-main...
## Expected behavior `sesman-start` should work regardless of the user shell ## Actual behavior Cider builds a string like this which has a lot of bash-specific escape characters. This probably...
Reading this https://docs.cider.mx/cider/troubleshooting.html#debugging-the-communication-with-nrepl I was able to output log messages/events to an emacs buffer. But how can i output those messages/events to a regular file?
The debugger simply fails if used in ClojureScript code, it would be nice for it to work. Here's a list of things to achieve that. If anyone can help with...
## Expected behavior completion works as usual, across imported namespaces ## Actual behavior when calling completion-at-point, only completions belonging to the current namespace are offered (after C-c C-k to compile...