This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-07-12
Channels
- # aleph (10)
- # beginners (79)
- # boot (81)
- # chestnut (3)
- # cider (9)
- # cljs-dev (336)
- # cljsrn (17)
- # clojure (121)
- # clojure-boston (1)
- # clojure-italy (4)
- # clojure-nl (1)
- # clojure-russia (218)
- # clojure-spec (32)
- # clojure-uk (98)
- # clojurescript (109)
- # cloverage (1)
- # core-async (5)
- # cursive (17)
- # datascript (15)
- # datomic (38)
- # editors (4)
- # emacs (6)
- # graphql (1)
- # hoplon (140)
- # instaparse (1)
- # jobs (2)
- # klipse (1)
- # leiningen (4)
- # lumo (2)
- # mount (103)
- # off-topic (3)
- # om (8)
- # onyx (19)
- # parinfer (32)
- # pedestal (3)
- # precept (32)
- # re-frame (33)
- # reagent (24)
- # remote-jobs (11)
- # rum (1)
- # spacemacs (1)
- # specter (37)
- # unrepl (4)
- # untangled (43)
- # vim (11)
sorry I don't understand what you would like to achieve
with the task above you can do boot cider dev
and the middleware will be loaded
Sorry for the confusion, can i run cider-jack-in for the boot project, load dev profile automatically?
np, yes, if you do jack-in with a modern cider (which version are you using?) you should not need any additional configuration
boot does not have profiles, just tasks
perfect
so just a jack-in should be enough
still not sure I understand...
jack-in should detect if you are running on boot or lein
and call the right command
Okay this was my workflow with lein, emacs, cider for development, there i don't need to run "boot cider dev" or lein run on terminal, all i used to do cider-jack-in, start the app in repl.
same in boot
if you have an error paste it here, you just need cider-jack-in
ok, but these are two problems
let's solve one by one
is it jacking in and ending up in user=>
?
so can you (in-ns 'your-namespace.core)
?
ok...sorry I meant if you can in-ns
in one of your namespaces of your app and call some function
in-ns
actually creates the namespace so you need to try to call something for real 😄
i replaced "your" with "my" when am entering here, not just copy paste 😛, what i tried is my project namespace.
ah ah ok, so it is on the classpath if you can execute a function
about the automatic change
you should pass --init-ns
to your repl task
you have two options, one is to modify how cider launches it, the second is to set the option with task-options!
in build.boot
@richiardiandrea fyi, I got live-reloading in webworkers with boot-figreload working, but it needed a custom boostrap script, as documented here: https://github.com/bhauman/lein-figwheel/wiki/Using-Figwheel-with-Web-Workers but as the I needed to use boot-cljs’ generated main the static script as in the example didn’t do and I decided to try to do it the proper way, which resulted in adding support for targeting webworkers in clojurescript, see https://dev.clojure.org/jira/browse/CLJS-2216
oh that super cool!
do you think we could use :preloads
for that script or something?
we could convert that script to a cljs one and do what we do in boot-cljs-devtools
for hooking it up with a switch or a custom conf entry in the .cljs.edn
file
oh ok, I have just checked out the patch, even better there 😄
so what we could do, and if you want to contribute it would be awesome, is to have a branch in https://github.com/arichiardi/figreload-demo with a worker
or in here for boot: https://github.com/yetanalytics/figwheel-worker-example
or both 🙂
let’s see if that patch is accepted in that form or if david wants to go with something like thomas heller suggests. I see pluses and minuses for both
Hey all, I'm having issue actually getting boot on my system
I have the boot.sh and make it executable and added it to my systems PATH but it still can't make use of the boot command
I can run the script via ./my_dir/boot.sh but that's about it
the filename must be boot
instead of boot.sh
if you want to use boot
command
Soooo...could I make an alias like alias boot='./boot.sh'?
You could, but much easier to just rename the file
Hmh, the install steps in readme don't say to rename the file, but the example command does that: curl -fsSLo boot
-o boot
says to save the file as boot
Updated the readme: https://github.com/boot-clj/boot/commit/84c363fe9c52c535e099e36d4fcd46ea9ed9fcc8
Tried that, it popped up and error I can't remember
could be about missing /usr/local/bin
Maybe. I'll just rename boot.sh
later and try it.
I gotta be somewhere in a hour. :P
I'm trying to have a project depend upon [org.clojure/clojure "1.9.0-alpha17" :scope "provided"]
Classpath conflict: org.clojure/clojure version 1.8.0 already loaded, NOT loading version 1.9.0-alpha17
If I change (in boot.properties) BOOT_CLOJURE_VERSION=1.9.0-alpha17, then I get a bunch of spec errors.... any ideas?
@tmarble is the entrypoint of the application boot?
perhaps you have code in your profile.boot that set-env! clojure?
in theory tho your setup sounds like it should work. boot uses 1.9.0-alpha17 for itself, then marks that version of clj as a dep to prevent other versions of clj from being loaded
hmm.. if i set BOOT_CLOJURE_VERSION=1.9.0-alpha17 and do NOT specify clojure in set-env! I get the spec errors
what does echo '(clojure-version)' | boot repl
report?
boot repl fails with BOOT_CLOJURE_VERSION=1.9.0-alpha17 in boot.properties... reverting to 1.8.0...
now with BOOT_CLOJURE_VERSION=1.8.0 and set-env! [org.clojure/clojure "1.9.0-alpha17"]
tmarble@cerise 329 :( boot repl
Classpath conflict: org.clojure/clojure version 1.8.0 already loaded, NOT loading version 1.9.0-alpha17
nREPL server started on port 43733 on host 127.0.0.1 -
REPL-y 0.3.7, nREPL 0.2.13
Clojure 1.8.0
OpenJDK 64-Bit Server VM 1.8.0_131-8u131-b11-2-b11
Exit: Control+D or (exit) or (quit)
Commands: (user/help)
Docs: (doc function-name-here)
(find-doc "part-of-name-here")
Find by Name: (find-name "part-of-name-here")
Source: (source function-name-here)
Javadoc: (javadoc java-object-or-class-here)
Examples from : [clojuredocs or cdoc]
(user/clojuredocs name-here)
(user/clojuredocs "ns-here" "name-here")
boot.user=> (clojure-version)
"1.8.0"
boot.user=>
I've got to run now, but I do hope to figure this out (in order to play with clojure.spec while using boot)
super weird. yeah, sorry, nothing wrong sticks out