This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-01-23
Channels
- # announcements (7)
- # babashka (11)
- # babashka-sci-dev (1)
- # beginners (8)
- # biff (1)
- # calva (8)
- # chlorine-clover (3)
- # cider (9)
- # clj-kondo (16)
- # cljdoc (9)
- # clojure (79)
- # clojure-australia (1)
- # clojure-dev (5)
- # clojurescript (24)
- # data-science (3)
- # datomic (2)
- # emacs (54)
- # fulcro (1)
- # graalvm (1)
- # jobs (5)
- # lsp (25)
- # malli (7)
- # meander (10)
- # off-topic (44)
- # other-languages (8)
- # portal (10)
- # remote-jobs (1)
- # sci (1)
- # shadow-cljs (6)
- # vim (4)
With Cider - I utilize these two functions primarily:
'cider-eval-defun-at-point
'cider-pprint-eval-defun-at-point
Sometimes, the focus automatically jumps into the output buffer. Is there a setting or variable I can set that disables this shift of focus?
More cider config:
(setq cider-interactive-eval-output-destination 'output-buffer)
(setq cider-redirect-server-output-to-repl nil)
(setq clojure-toplevel-inside-comment-form t)
(setq cider-repl-pop-to-buffer-on-connect nil)
if so, that automatically highlights the repl buffer. There's a defcustom to prevent that
no, I prefer to keep things out of the REPL buffer -
most of the time the two fns listed above work fine - but it will randomly hop me over into the output buffer upon eval
Then no idea sorry. That was the one thing I could think of that puts you in the repl buffer
I think doom-emacs does that by default @edward.ciafardini,.maybe debug what they change
I am trying to setup clojure-lsp
to use some of it’s feature. But I am getting a conflict with cider
, where the arity information that appears at the buttom of the screen gets substituted by and error about the arity of the function bein incomplete. I don’t know how to disable this as it is much less useful than displaying the arity of the function. Any ideas?
This I my setting at the moment (I knoew they look messy :S)
(add-hook 'clojure-mode-hook 'lsp)
(add-hook 'clojurescript-mode-hook 'lsp)
(add-hook 'clojurec-mode-hook 'lsp)
(setq gc-cons-threshold (* 100 1024 1024)
read-process-output-max (* 1024 1024)
treemacs-space-between-root-nodes nil
company-minimum-prefix-length 1
lsp-enable-on-type-formatting nil
;; lsp-enable-indentation nil ; uncomment to use cider indentation instead of lsp
;; lsp-enable-completion-at-point nil ; uncomment to use cider completion instead of lsp
)
(setq lsp-lens-enable t)
(setq lsp-signature-mode nil)
(setq lsp-ui-mode nil)
(setq lsp-ui-doc-show-with-cursor nil)
(setq lsp-headerline-breadcrumb-enable nil)
(setq lsp-ui-sideline-enable nil)
(setq lsp-modeline-code-actions-enable nil)
(setq lsp-signature-render-documentation nil)
(setq lsp-signature-auto-activate nil)
(setq lsp-completion-enable nil)
(setq lsp-eldoc-enable-hover nil)
This should disable cider eldoc integration to use lsp only:
(setq cider-eldoc-display-for-symbol-at-point nil) ; use lsp
and you probably want to enable lsp-eldoc-enable-hover
to show the arity of the functions on the bottom
Also, I personally like to enable the lsp-modeline-code-actions-enable
as the UI change is minimal and very useful to know if there is a code action available on that line
Still getting the same arity error displayed on the minibuffer
The arity information pops for a second before being replaced by the error message.
hum, sounds like a cider feature that I'm not aware of, maybe cider-eldoc-display-context-dependent-info
? try disabling that one
Actually even when cider is not running I get this error
I am using prelude
with some custom configurations of my own
maybe you don't have flycheck or have your emacs configured to show the diagnostics on the bottom
yes, I have flycheck
where do I find that?
it’s set to auto
if I disable it the error message goes away, and I can see the arity doc
odd, so we need to understand why flycheck is showing it on the bottom and not on the buffer
does this look right?
hum, maybe that lint is from those custom clj-kondo flycheck runners, I'd suggest disabling (or even uninstalling) both clj-kondo-* to check if the issue is fixed
didn’t work
but this did
(require 'flycheck)
(setq flycheck-display-errors-function nil)
should that be right?
I still see the errors with flycheck-list-errors
so I suppose that should be fine
oh haha
that’s probably why
well, thanks for the help, pretty sure I would be getting nowhere without it
inlining the error?
yeah, it prints the warnings/errors/info on the line when hovering the line: https://emacs-lsp.github.io/lsp-ui/#lsp-ui-sideline