This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-10-06
Channels
- # aleph (15)
- # announcements (2)
- # babashka (121)
- # beginners (62)
- # biff (6)
- # cherry (2)
- # cider (51)
- # clerk (30)
- # cljs-dev (5)
- # clojure (77)
- # clojure-austin (2)
- # clojure-europe (10)
- # clojure-germany (6)
- # clojure-nl (1)
- # clojure-norway (19)
- # clojure-romania (1)
- # clojure-uk (3)
- # clojurescript (16)
- # core-typed (7)
- # cursive (17)
- # datomic (12)
- # deps-new (11)
- # emacs (7)
- # events (2)
- # fulcro (5)
- # honeysql (2)
- # hyperfiddle (32)
- # introduce-yourself (1)
- # jobs-discuss (2)
- # membrane (18)
- # missionary (2)
- # music (5)
- # polylith (7)
- # reagent (26)
- # releases (5)
- # testing (32)
- # tools-build (14)
- # tools-deps (7)
- # xtdb (8)
is it possible to fine-tune eldoc (in the context of eglot) such that I could choose which documentation functions are called for the echo area and which for the actual doc buffer?
looking at my current eldoc-documentation-functions
, it looks like:
- eglot-signature-eldoc-function
provides a nice one-line function signature of the clojure-function-at-point.
- eglot-hover-eldoc-function
provides the whole docstring in markup.
- and finally flymake-eldoc-function
provides info on errors on the line.
Ideally, I'd like to see the function signature (`eglot-signature-eldoc-function`) and possibly any errors (`flymake-eldoc-function`) in the echo area, but if I invoke e.g. eldoc
on some symbol I'd like to see just the documentation (`eglot-hover-eldoc-function`).
Just in case someone else is interested: I ended up hacking together something awful like this: https://github.com/casouri/eldoc-box/issues/90#issuecomment-1751968271
As of lately I've been suggesting some tweaks to company-mode
, and its maintainers have been very generous in carefully implementing those.
Especially after today's snapshot (`<tel:202310061438|20231006.1438>`) I'd recommend to customize company-auto-update-doc
to t
. This way, CIDER will automatically show the docstring for the current candidate (otherwise one had to hit <f1>
each time for that to happen).
We have documented that over https://docs.cider.mx/cider/usage/code_completion.html#company-mode-installation as well.
![emacs](https://emoji.slack-edge.com/T03RZGPFR/emacs/f104ce848dbeae69.png)
I know corfu is supposedly the hip option now, but honestly I don't know what's possibly wrong with Company. It's been my trusty tool for quite a few years. It feels like a really battle-hardened solution. Corfu broke easily for my initial testing - it left some stray overlays. I don't like overlays to begin with tbh. Emacs has some limitations as for graphics, IMO it's drastically simpler to embrace those limitations instead of pretending Emacs is an IDE from the early 00's :)
I only know Corfu as a holiday destination which I have never visited 😆 , so I appreciate the work to enhance Company-mode (especially the Cider documentation). Thank you.