This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-12-02
Channels
- # adventofcode (5)
- # arachne (2)
- # bangalore-clj (1)
- # beginners (8)
- # boot (195)
- # cider (28)
- # cljs-dev (35)
- # cljsrn (4)
- # clojure (295)
- # clojure-brasil (5)
- # clojure-gamedev (2)
- # clojure-greece (2)
- # clojure-korea (13)
- # clojure-russia (60)
- # clojure-spec (58)
- # clojure-uk (92)
- # clojurescript (31)
- # clojurex (4)
- # css (1)
- # cursive (13)
- # datomic (40)
- # devcards (2)
- # emacs (17)
- # events (1)
- # flambo (3)
- # garden (9)
- # hoplon (31)
- # jobs (3)
- # klipse (1)
- # lein-figwheel (1)
- # london-clojurians (1)
- # luminus (2)
- # mount (36)
- # off-topic (13)
- # onyx (8)
- # pamela (1)
- # pedestal (1)
- # planck (3)
- # proto-repl (16)
- # protorepl (11)
- # re-frame (78)
- # reagent (4)
- # rethinkdb (6)
- # ring-swagger (1)
- # specter (8)
- # untangled (10)
- # vim (1)
this will show the nrepl messages going back and forth and we can try to see where it gets the symbol hi
if you ever want to dig a little in the future, check out nrepl-toggle-message-logging
(For the record I was on the Nov 27 snapshot when I was facing the issue and it has gone away in Dec 01 snapshot)
nrepl-messages is silent, and same 'Symbol's value as variable is void: hi', in a different project...
Debugged my init.el and tracked it down to " after loading cider-eval-sexp-fu things stop working". Disabling that made everything work again, I think.
@iku000888 what did you disable? I didn't really follow that
I disabled a package called 'cider-eval-sexp-fu' which apparently contained the breakage with latest cider/some other package I was using. Sorry for the mumbling!
Everything is good, without the fancy flashing when I eval sexp's, but I can totally live with out them
@juhoteperi Thanks, but I'd prefer not to have to include style related code in my codebase. Think I'll stick to defining each symbol explicitely in my .spacemacs
PRs to the libraries would also be good solution in long term
There was already a PR about this (om.dom) and it was rejected by the library author. I can understand why tbh, I'm not sure metadata is the right approach. Ideally you want to leave this stuff to each individual and their editor and keep the code clean.