is there a cider function to dismiss the stack trace?

@kiemdoder what do you mean? like to just dismiss the buffer?

hi @dpsutton, sometimes a new window is created for the stack trace and when I kill the stack trace buffer I'm still left with the window

I noticed that when I evaluate some code in a clj file that causes a stack trace the stack trace is dismissed when I fix the code and evaluate it again. That made me think that maybe there is a cider function to dismiss the stack trace. I looked through the cider functions but could not find one yet.

I always hit q in the buffer to bury it.

are you killing the buffer with emacs commands?

the cider error buffer is a cider ancillary buffer. you can see how these things are created here:

(defun cider-make-popup-buffer (name &optional mode ancillary)
      "Create a temporary buffer called NAME using major MODE (if specified).
    If ANCILLARY is non-nil, the buffer is added to `cider-ancillary-buffers'
    and automatically removed when killed."
      (with-current-buffer (get-buffer-create name)
        (kill-all-local-variables)
        (setq buffer-read-only nil)
        (erase-buffer)
        (when mode
          (funcall mode))
        (cider-popup-buffer-mode 1)
        (setq cider-popup-output-marker (point-marker))
        (setq buffer-read-only t)
        (when ancillary
          (add-to-list 'cider-ancillary-buffers name)
          (add-hook 'kill-buffer-hook
                    (lambda () (setq cider-ancillary-buffers (remove name cider-ancillary-buffers)))
                    nil 'local))
        (current-buffer)))

this is in cider-popup.el

The "q" key was the thing I was looking for. Thanks a lot

awesome.

I notice now that "q" is used elsewhere in emacs as well like dismissing a dired window for instance

Yeah, like less