This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-05-27
Channels
- # announcements (2)
- # beginners (85)
- # boot (4)
- # calva (4)
- # cider (14)
- # cljdoc (8)
- # cljs-dev (5)
- # cljsrn (10)
- # clojure (101)
- # clojure-europe (1)
- # clojure-italy (6)
- # clojure-nl (12)
- # clojure-spec (4)
- # clojure-uk (71)
- # clojurescript (119)
- # core-async (20)
- # cursive (1)
- # datascript (2)
- # duct (3)
- # emacs (19)
- # fulcro (150)
- # graphql (1)
- # hoplon (2)
- # instaparse (2)
- # jobs (1)
- # jobs-discuss (11)
- # joker (9)
- # luminus (6)
- # lumo (1)
- # off-topic (33)
- # onyx (1)
- # quil (1)
- # re-frame (23)
- # reagent (11)
- # robots (2)
- # rum (6)
- # sql (1)
- # test-check (10)
- # unrepl (1)
@bozhidar nope, there's an explicit call to cider--kw-to-symbol
in both those functions which does the coercion, thing-at-point recognizes them as different entities.
You’ll have to go through the history to see what triggered the addition of this conversion.
I traced it back to this issue from 2015: https://github.com/clojure-emacs/cider/issues/1220
Didn't realise that there were libraries out there that used keywords to refer to similarly named vars/functions - I wonder how common of a practice this is (as mentioned in the issue discussion too)
when I'm working in a cljs project, say I want to view a value (created from a def), why does it give me WARNING: Use of undeclared Var
but then it prints the value to the REPL and how do I make the warning go away?
Is there a special reason why the README specifically mentions lein and boot but not the CLI tools or is it just missing a PR?
@anantpaatra Just an oversight.
They are properly documented in the manual, though. See https://cider.mx/cider/basics/up_and_running.html
CIDER appears to be mostly working fine but is no longer automatically creating ns forms when I create a new source file. I can't tell because they're in an unusual directory structure (`server/test/project/xyz.clj` and server/src/project/abc.clj
) -- how do I start debugging that?