This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-05-31
Channels
- # admin-announcements (4)
- # alda (3)
- # aws (1)
- # beginners (2)
- # boot (33)
- # braid-chat (4)
- # braveandtrue (20)
- # cider (52)
- # cljs-dev (13)
- # cljsrn (55)
- # clojure (111)
- # clojure-belgium (4)
- # clojure-brasil (6)
- # clojure-dusseldorf (1)
- # clojure-greece (116)
- # clojure-mexico (1)
- # clojure-nl (3)
- # clojure-russia (56)
- # clojure-spec (72)
- # clojure-uk (13)
- # clojurescript (66)
- # community-development (2)
- # component (24)
- # core-async (1)
- # cursive (19)
- # datomic (27)
- # devcards (5)
- # emacs (1)
- # funcool (34)
- # hoplon (313)
- # jobs (1)
- # lein-figwheel (11)
- # luminus (5)
- # mount (30)
- # off-topic (63)
- # om (375)
- # onyx (67)
- # perun (8)
- # proton (1)
- # reagent (4)
- # rum (1)
- # specter (55)
- # spirituality-ethics (7)
- # test-check (2)
- # untangled (34)
- # yada (20)
…..huh. Well… that damn sure would expain my “no repl” results. I also definitely got the impression from the cider docs that cider would “do the right thing” — given a couple deps (piggieback, for instance) it would fire up a rhino
repl for you.
I’ve been relying on this, fwiw http://cider.readthedocs.io/en/latest/up_and_running/#clojurescript-usage
@malabarba: I'd love to chat sometime about nREPL messages for ClojureScript compile warnings as well as Compile Exceptions.
Oh lord, got it — something about clj-refactor
is interfering with starting the clojurescript repl.
bhauman: you probably already know this, but figwheel is neat as heck 😄 Thank you so much for it!
@bhauman sure. You mean like getting cljs exceptions to display like we display Clojure exceptions?
malabarba: ah, yep. Blowing away and re-installing clj-refactor and refactor-nrepl seem to have done it. Thanks!
@malabarba: yeah, actually there are 3 different things here, javascript runtime exceptions and this should be pretty easy to fix.
Then compiler exceptions, these are syntax and reader errors and often come with column and line information along with a brief explanation.
Then there are compiler warnings. There can be multiple warnings per compile and these come with a description and location information as well.
@hans: Turns out it's not a cider bug. Dots in var names is simply not supported. Or maybe it's a bug in clojure.core.
Just boot up a plain lein repl
. Then evaluate (def a.a 1)
. And try to evaluate (resolve 'a.a)
.
@bhauman: Handling this stuff on the Emacs side should be simple. In fact, all of the exceptions should be trivial, only the warnings might be more work.
The link, in case anyone else was following the conversation: https://github.com/clojure-emacs/cider/issues/1771
@malabarba: interesting. thank you for the clarification. i wonder if there is a formal definition of the characters that a symbol may contain. clojure should probably refuse to use unsyntactic symbols in any case.
@malabarba: case closed, thanks 🙂