This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-25
Channels
- # aws (2)
- # bangalore-clj (2)
- # beginners (90)
- # boot (89)
- # bristol-clojurians (1)
- # cider (23)
- # cljs-dev (48)
- # cljsjs (2)
- # cljsrn (3)
- # clojure (118)
- # clojure-argentina (3)
- # clojure-austin (8)
- # clojure-czech (1)
- # clojure-dev (18)
- # clojure-ireland (1)
- # clojure-italy (4)
- # clojure-russia (6)
- # clojure-spec (75)
- # clojure-uk (224)
- # clojurescript (103)
- # core-async (28)
- # cursive (3)
- # datascript (7)
- # datomic (15)
- # dirac (30)
- # emacs (14)
- # events (3)
- # figwheel (1)
- # hispano (1)
- # hoplon (176)
- # lambdaisland (1)
- # lein-figwheel (6)
- # off-topic (21)
- # om (7)
- # onyx (2)
- # pedestal (6)
- # re-frame (4)
- # reagent (15)
- # spacemacs (67)
- # specter (13)
- # testing (9)
- # untangled (65)
- # vim (6)
- # yada (1)
hey guys, so I have this:
(notify :audible true :theme "woodblock"
:visual true :title “my-silly-project”)
It fails to run terminal-notifier when hits the exceptionI'm not sure what I changed. https://github.com/magomimmo/modern-cljs/blob/master/doc/second-edition/tutorial-02.md#browser-repl-brepl is suddenly not working for me: "boot dev" is running on localhost:3000 with <ws://localhost:54222> boot repl --client // (start-repl) is saying conection is at <ws://localhost:54239> and my browser, upon visiting localhost:3000 , is trying to connect to <ws://localhost:54179>
@qqq, the answer with these issues is usually to hard-reload the browser
in this case, it was becuase the two boots "talk" to each other via ./target/adzerk/boot_reload.cojs (which is one of them telling th eother which port to listen to)
(the two boots as in how "boot dev" and "boot repl -c // (start-repl)" agree on which port the ws for brepl is listening on)
============== I do have a new question though: I have two computers. I want my browser running on a different computer from boot // so now I need to change "<ws://localhost:54288>" to "<ws://ip-address:port>" how do I tell boot "point the ws at a particular ip address, rather than localhost" ?
why do you want that?
here's the case: I have two laptops; I want emacs/boot on one laptop, and I want the browser displaying on a different laptop
not sure if it's possible with cljs-repl
instead of "boot -h" // which suffers a jvm startup time every time I look something up is it posisble, inside a "boot repl" to lookup the documentation ?
so I wnat to lookup documentation inside a boot repl, instead of "lookup documentation via calling boot from the shell"
(doc boot.task.built-in/watch)
for anyone who's curious, it's (cjs-repl :ip (.getHostAddress (java.net.InetAddress/getLocalHost)))
is there a way to tell the cljs task to put the output somewhere besides "./out" ? I want it to be placed in "./gen/out"
is it possible to stuff "boot dev" and "boot repl -c // (start-repl)" into a single repl session? I'm okay if the output of the two "overlap"
@qqq you can move stuff around in the fileset arbitrarily with the sift
task
@alandipert: I'm not sure how this helps me
similarly, when I run "(boot (dev))", it "takes over the console, andI can't run anything else"
oh, i don't know how to do the second thing... this is in reference to moving files from out
i don't use any cljs repls but a thing to try maybe is (def f (future (boot (dev))))
and then (start-repl)
maybe?
i don't know what your dev task does or what the start-repl function is so ymmv
then to kill the build you can do (future-cancel f)
since (star-trepl) depends on the other process ot generate target/main.out/adzerk/boot_cljs_repl.cljs
perhaps, I should rephrase my question sas follows: ========== right now, I have to dl M-x eshell // boot dev is there a way to in emacs, direclty do "run boot dev and send its output to this buffer" ?
I don't have to control which buffer the output it goes to; "run boot dev, and give me a buffer with its running output" is perfectly fine as well
probably M-x (e)shell is most straightforward
yeah if you do a little bit more elisp you can make a function that creates a buffer and sends the output to it
@qqq cider already does that for lein, but does not have support for boot (but an issue is open), are you using cider?
Also, can you share your emacs lisp only version, I am curious 😀😀
@richiardiandrea : my entire 'ide' at the moment is just inferior-lisp + clojure-mode + a hook of
(defun my-clojure-setup()
(setq-local inferior-lisp-program "boot repl -c")
(define-key clojure-mode-map (kbd "C-x C-e") 'lisp-eval-lastp-sexp))
the stuff that makes me execited are:
(1) how prorgrammable boot is
(2) a weird setup where my entire project is a single or-gmode file, which I then tangle to get all the source code + configs
(3) using lein + cider, I never goot brepl / cljs-ack-in to work ... with boot, I have bREpl not only working -- but also working in a way I can program / customize it
so yeah -- not much substance, alot of excitement thoughso many tools and environments want to take away programming because they think it's not good for you
but they're wrong! need to be able to program everything!
a disturbing trend
you know what's the best way to fix it? build programmable tools -- get programmers who use programmable tools to be 10x as efficient -- and let darwanian evolution / market efficiency take care of the rest 🙂
at least it defers the mindset. because inevitably, a % of the programmers handed the programmable tool have the idea to remove the programming before giving it to other programmers
Agree, @qqq I like your setup! I have been thinking of switching from cider to inf-clojure. Also, here is the issue I was taking about https://github.com/clojure-emacs/cider/issues/1881
@richiardiandrea : the thing that really clicked for me was when I realized: (1) I wasn't using most of cider's power (2) all I really need are "eval last sexp" and "eval entire buffer" (3) 99% of my debugging involves (1) creating a hiccup [:pre ] element, and shoving a pretty-print in it -- however nice cider inspect is, I just prefer to see the entire data, in the UI/browser, at where it's being used
Yeah I tend to use some features, but not all actually. I like the switching namespace and lord feature for instance.. and tests mostly. Nothing you cannot add to inf-clojure to be honest
the other nice thing about adding things piece by piece (and this is why I use from scratch bindings rather then apsacemacs) is that you can add new features confidently, without fear of "oh shit, does this break some piece of code I'm not even ware of -- which large projects tend to give of the vibe of" I should also admit, at this point, we should probably move to #off-topic, as we've pulled this conversation quite far from #boot 🙂
Yeah indeed 😄 t's OK, I am a big emacs and boot fan so I guess my curiosity stemmed from understanding how much effort would require to move to inf-clojure
And of course I would not want to be less efficient 😀
Wasn’t there an option that would do me something like boot -X '(println “abc”)'
ah, boot -i apparently
yes -i
Hi -- has anyone had an issue similar to this: Using boot to run a clj/s test suite on CircleCI (with some clojure.spec tests). When tests fail, CircleCI does not recognize and says tests were successful. I think it's because an exit code of 0 was returned but I'm wondering if there's more going on.
Hi. How do I make boot
to use Clojure 1.8.0?
@andrewboltachev you can set BOOT_CLOJURE_VERSION=1.8.0, set it in ~/.boot/boot.properties, or set in in a director-local boot.properties
@alandipert thanks, but is 1.7.0
the default?
not sure, it depends on when you installed boot
through 1.8.0 is supported tho
I've just re-installed it (i.e. sudo rm /usr/local/bin/boot
and then install)
but seems still it's 1.7.0. Well, boot.properties
is also an option
~/.boot/boot.properties is the canonical 'global' place to set it
@andrewboltachev you probably have a boot.properties file already
@micha ah, yes! gotcha
@andrewboltachev i do sth like boot -u > boot.properties.
i.e. suppose it works in lein, do I need to do anything special to get boot to support macros?
@qqq I assume in cljs? The answer is no, support is handled by the compiler, be sure that the files are on the classpath only
if I have (set-env! :source-paths #{"src/"}) and the *.cljc file is in src/foo/bar.cljc , is this the same as "on the classpath only" <-- no idea what this phrase means
@qqq yes it should be ok
also, but I don't think it matters, I usually use "src"
third thing, are you using :require-macros
or :include-macros true
for your namespace?