This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # adventofcode (1)
- # bangalore-clj (1)
- # beginners (118)
- # boot (39)
- # cljs-dev (6)
- # cljsrn (1)
- # clojure (62)
- # clojure-mke (1)
- # clojure-nl (6)
- # clojure-russia (51)
- # clojure-spec (8)
- # clojure-uk (9)
- # clojurescript (101)
- # code-reviews (1)
- # cursive (2)
- # datascript (9)
- # datomic (80)
- # emacs (4)
- # hoplon (27)
- # jobs-discuss (1)
- # off-topic (1)
- # om (1)
- # onyx (18)
- # protorepl (2)
- # re-frame (13)
- # reagent (13)
- # rum (9)
- # test-check (23)
I'm exploring packaging an official clojure docker image w/ boot instead of lein pre-installed. But I'm having trouble figuring out how to install a specific version of boot. I want to script the installation of boot 2.7.0 (apparently the latest release?). How would I go about doing that in such a way that it will still install 2.7.0 even when a newer version is released?
I'm a little stumped I keep getting unable to resolve symbol when I have required it. https://gist.github.com/CommonCreative/0ed06d8ddfd5dbde01d14b2e335678b6
The execption thrown
clojure.lang.Compiler$CompilerException: java.lang.RuntimeException: Unable to resolve symbol: defstyle in this context, compiling:(vbn/web.cljc:12:1) java.lang.RuntimeException: Unable to resolve symbol: defstyle in this context
Managed to get it working with just calling by the full namespace each time. Not sure why it's not working the way it should though
@grounded_sage you're just requiring the macro in cljs and that error seems to be a Clojure compiler exception
@cap10morgan since 2.4.2 or so the binary is merely a shim and all versions since that can be used by just setting
BOOT_VERSION. You can set this either via env var,
hi, can anyone recommend a starting point for a new boot node.js/NPM module project?
Googling has gotten me nowhere, so - I have some calls to
boot.util/info inside a pod. From a command line repl, these are printed, but from a cider repl, they are not. I’m not sure if I should be looking for a knob to fiddle with in boot, or in cider, or if I’m just out of luck - does anyone have any tips on where to look?
in the terminal, I get output, but connecting to the same repl process in cider results in no output
yeah so if you see the info logs then I'd say that's a sign for cider somehow swallowing the stdout of the repl server it starts
same - from a normal task it works, but in a pod, it doesn’t. I’m actually dealing with perun here, btw. The missing output is from tasks like
markdown that call
info from a pod.
just to be clear, I’m calling
boot repl from the command line, and then
M-x cider-connecting to it from emacs. Then I
(boot (dev)) from cider. In this case, I get non-pod output in emacs, and pod output on the command line.
So pods are totally isolated:
*out* in one pod is a different var than
*out* in another pod. You cannot make dynamic bindings into pods.
@bhagany at least in the immediate moment, yeah 😕 you should open an issue though, maybe it's something that can be improved
I don't have any ideas how it could be done right now but I'm sure someone will 🙂
new discovery: when jacking in, pod output does end up in emacs, but it’s in the server buffer, not the repl buffer