This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-09-14
Channels
- # 100-days-of-code (4)
- # announcements (1)
- # beginners (63)
- # boot (22)
- # braveandtrue (104)
- # calva (3)
- # cider (12)
- # cljs-dev (53)
- # cljsjs (3)
- # cljsrn (1)
- # clojure (180)
- # clojure-dev (14)
- # clojure-italy (4)
- # clojure-nl (11)
- # clojure-spec (15)
- # clojure-uk (60)
- # clojure-ukraine (1)
- # clojurescript (118)
- # clojutre (3)
- # core-async (12)
- # core-logic (17)
- # cursive (19)
- # datomic (45)
- # devcards (4)
- # emacs (7)
- # figwheel-main (218)
- # fulcro (27)
- # funcool (3)
- # graphql (1)
- # jobs (4)
- # leiningen (57)
- # off-topic (71)
- # pedestal (2)
- # portkey (17)
- # re-frame (5)
- # reitit (4)
- # remote-jobs (2)
- # ring (11)
- # rum (2)
- # shadow-cljs (14)
- # specter (11)
- # sql (34)
- # tools-deps (23)
interesting, if you add -A:fig:build
as an alias with dir-locals to the var cider-clojure-cli-global-options
it successfully creates a repl and connects but it does so in the server buffer and you can't interact with it
with the latest cider, when I go to source to a file that's not in the current project (such as in a library), I keep getting messages about cider sessions not being linked if I attempt to jump to source for something inside that namespace
any ideas what's going on?
@tanzoniteblack it is a known problem, I do not recall if it's been fixed on master
or not
thanks for letting me know, @richiardiandrea
do you know if there's already a ticket open for it that I can track?
I'll go take a look for that and post it here if I find it
https://github.com/clojure-emacs/cider/issues/2446 seems to cover this use case
I think there is one...possibly a closed one? ... yep that one