This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-07-12
Channels
- # announcements (1)
- # aws (1)
- # babashka (63)
- # beginners (108)
- # calva (12)
- # cider (6)
- # cljdoc (2)
- # cljsrn (33)
- # clojure (150)
- # clojure-europe (28)
- # clojure-nl (13)
- # clojure-spain (1)
- # clojure-spec (8)
- # clojure-uk (25)
- # clojurescript (16)
- # conjure (7)
- # cursive (7)
- # datomic (15)
- # duct (2)
- # eastwood (2)
- # figwheel (1)
- # figwheel-main (1)
- # fulcro (6)
- # graalvm (1)
- # graalvm-mobile (1)
- # helix (6)
- # honeysql (23)
- # integrant (6)
- # introduce-yourself (4)
- # jobs (10)
- # lsp (132)
- # malli (4)
- # meander (1)
- # membrane (1)
- # off-topic (223)
- # pathom (23)
- # pedestal (3)
- # re-frame (18)
- # reagent (13)
- # releases (1)
- # remote-jobs (2)
- # shadow-cljs (68)
- # tools-deps (217)
- # vim (19)
- # xtdb (79)
Started to browse old PRs just for the nostalgics. This is a gem! https://github.com/BetterThanTomorrow/calva/pull/52
Told you that defun was sweet Paredit legacy, @U01LFP3LA6P ! 😍
Tried to upgrade to mentioned version & enable code lens in my calva. It works, but I get a bit different appearance:
1. reg-sub
has same color as re-frame
(green). Tried switching between a couple different color themes, but both those symbols always share the same color. Is this important difference?
2. the 2 references
part doesn't get shown just after the keyword (on the same line), but it's placed on its own line, either just above keyword (if on its own line) or above the whole (re-frame/reg-sub
form (if the keyword and re-frame/reg-sub
are on the same line). Unfortunately this breaks the visual flow and wasted space.
It's a nice feature, but I'd definitely rather have the 2 references part
just after the keyword, as shown on ericdallo's screenshot. Any idea what needs to be changed, so that I get the same appearence as on the screenshot?
this is how it behaves when the keyword is on the same line as the reg-sub fn
Btw it's very handy feature, as it nicely pinpoints if you have some deprecated subscription registered, which is no longer being used anywhere. Neat!
Hello! 1. This is probably related with VSCode syntax highlighting as calva doesn't use semantic tokens yet, check this issue: https://github.com/BetterThanTomorrow/calva/issues/1231 2. this is a feature that AFAIK only emacs and vim have as default, showing the code lens at the end of line, not sure if VSCode has it via some flag c/c @U9A1RLFNV @U0ETXRFEW
oh, so the screenshot that you posted doesn't come from calva, @UKFSJSM38?
I suggest you open an issue on calva to support that if it doesn't support it already
ok, now it makes perfect sense 🙂 funny that those screens look that much similar 😄