This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-06-30
Channels
- # announcements (40)
- # babashka (41)
- # beginners (32)
- # calva (15)
- # clara (8)
- # clj-kondo (14)
- # cljs-dev (30)
- # clojure (37)
- # clojure-dev (8)
- # clojure-europe (21)
- # clojure-norway (21)
- # clojure-uk (4)
- # clojured (3)
- # clojurescript (4)
- # community-development (10)
- # core-async (13)
- # cursive (23)
- # datomic (15)
- # emacs (9)
- # fulcro (3)
- # google-cloud (4)
- # graphql (24)
- # gratitude (2)
- # holy-lambda (4)
- # honeysql (5)
- # hyperfiddle (9)
- # keechma (1)
- # klipse (5)
- # lsp (23)
- # malli (4)
- # missionary (32)
- # pathom (28)
- # re-frame (2)
- # reagent (40)
- # reitit (17)
- # releases (2)
- # remote-jobs (1)
- # shadow-cljs (25)
- # specter (3)
- # vim (19)
- # xtdb (41)
ok checked with describe-char and I think the issue is the face has a familiy attribute Monospace Serif
maybe I don't have such a face installed
Hi folks. In clojure-mode
, when I run sexp-at-point
before parenthesis, it works. However, when I run it before a map, as in |{:foo :bar}, where | is the point, it returns nil. Why is that? How can I reliably get the next sexp?
You could try
(let ((beg (point))
(end (save-excursion
(clojure-forward-logical-sexp)
(point))))
(buffer-substring beg end))
Nice, thanks. I thought that each major mode defined its own sexp-at-point
, but I suppose it’s not the case.
I feel like lsp and cider are fighting over showing me the function signature and they are both losing. Is anyone else getting behavior where it flips back and forth between what looks like one or the other?
Check the conflict section https://emacs-lsp.github.io/lsp-mode/tutorials/clojure-guide/#hover
@UKFSJSM38 thanks! ill give that a try.