This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-02-15
Channels
- # aatree (23)
- # admin-announcements (13)
- # announcements (3)
- # beginners (49)
- # boot (50)
- # braid-chat (1)
- # braveandtrue (37)
- # cider (72)
- # cljs-dev (25)
- # cljsjs (6)
- # cljsrn (37)
- # clojure (78)
- # clojure-berlin (8)
- # clojure-greece (1)
- # clojure-ireland (2)
- # clojure-madison (14)
- # clojure-new-zealand (2)
- # clojure-poland (10)
- # clojure-russia (149)
- # clojured (2)
- # clojurescript (49)
- # community-development (6)
- # core-async (37)
- # cursive (1)
- # data-science (1)
- # datomic (30)
- # emacs (4)
- # euroclojure (1)
- # funcool (1)
- # graclj (1)
- # hoplon (17)
- # jobs (2)
- # jobs-rus (45)
- # ldnclj (6)
- # mount (12)
- # off-topic (124)
- # om (270)
- # onyx (131)
- # parinfer (70)
- # perun (2)
- # proton (168)
- # re-frame (32)
- # reagent (29)
- # ring-swagger (8)
- # testing (9)
- # yada (39)
I am getting
ERROR: Unhandled REPL handler exception processing message {:op init-debugger, :print-level 10, :print-length 10, :session f10681b1-e8f4-48c6-bbc9-869f5ec1d54a, :id 7}
java.lang.IllegalStateException: Can't set!: *data-readers* from non-binding thread
whenever I cider-connect
from emacs?I am wondering if it is related to this http://hoplon.discoursehosting.net/t/question-about-data-readers-with-datomic-and-boot/99
Your can't Set! error looks like a thread binding issue. I assume you are using .clj? The problem is that data-readers was not bound on the thread you were trying to Set! on. To make a wild guess, you may be trying to use thread-local variables in a situation where the binding can not be thread-specific?
@samedhi Because of the h* * notation, I assume you have a dynamic variable. See http://clojure.org/reference/vars
Hi folks. Since it is by no means obvious (at least to me) how to (effectively) use the built-in tasks I started adding some simple examples at https://github.com/boot-clj/boot/wiki/Built-in-Tasks. I think it would be very helpful to newcomers to have a bunch of such examples.
Hi. I'm getting funny new errors running boot 2.5.5: Assert failed: The :source-paths, :resource-paths, and :asset-paths must not overlap.
. This is as soon as I try to define :source-paths
. If I define none of them it's ok (well, except the paths aren't defined) but as soon as I add :source-paths #{"src/main"}
it fails.
@jannis using bootlaces?
@jannis: bootlaces sets resource-paths to src
so that could cause this kind of thing
Thanks @martinklepsch
@jannis: https://github.com/adzerk-oss/bootlaces/commit/46973d71bd7d176a8e8b15278942555bf6f0e2bc
you can pass a :dont-modify-paths?
thing if you want to keep bootlaces around
@martinklepsch: Yep, already found out about that. Cool
Hey all
I know I can send forms from an editor to a repl, but what about the reverse? If I repl up a function I really like, can I say “ok now drop this function into the source code for this namespace”?
Copy-and-paste is the way to go. If you’re using Smartparens in Emacs/Spacemacs, you can just hit CTRL-OPTION-w and it’ll copy an entire form
but @amonks it is a useful idea for cider
's guys!
Hello @joshua.d.horwitz . Welcome.
@richiardiandrea, I suppose but Emacs doesn’t show cursors in non-active windows so you’d never be quite certain where’d it pop over to.
you could send symbol from the repl, meaning, given a symbol, fetch the source and materialize a function in my code buffer
What I do is craft functions, et. al, and send-and-eval-to-repl repeatedly rather than write then in the REPL and then insert into code.
@akiva: I do the same
but everybody is different 😄
for example I don't evaluate inline, I prefer to see the thing I am evaluating in the repl
Yeah. that’s been my style, too, but I’m trying to get into CIDER’s debugging. It’s kind of flaky currently in Spacemacs though.
cider has added a new more for debugging that it's awesome!
cider-enlighten-mode
or something
Yeah. I just need to do the extra tooling to get away from losing all local variables when reloading namespaces.
yeah, that bugs me as well, i put all the things I need in a comment and just re-eval one by one
yes true that, but I was more thinking of things you need for a smaller part, not system related, maybe some test data for a function
Yeah. I just know that the namespace reloading is smarter. Sometimes cider-refresh
blows away local def
s and require
s; sometimes it doesn’t.
Nevermind, it was solved thanks to the info at https://github.com/boot-clj/boot/wiki/Configuring-Boot#on-ci-servers