Fork me on GitHub

I just put up a new blog post (writing a FUSE + REST api integration in Clojure to show REST API results in a local FS):

🎉 6

Had no idea writing a fuse implementation was relatively straightforward. Now I’m wondering what other things I could represent as file systems…


I think it makes a great bridge / abstraction over more complicated data protocols like networking and such. You could even provide a fuse system to micro service users instead of an sdk for instance , and let them interact with records via their language of choice, even if it didn't support networking


I am asking for feedback I made a library to validate form inputs in CLJS with spec and fn. I would love to know if you will use it and get constructive feedback on #clojurescript channel!


Chlorine 0.0.6 is available -- a Clojure(Script) plugin for Atom, that works with a Socket REPL -- -- all follow-up to #chlorine please (I'm not the creator but I am an active user and recently blogged about my switch to Chlorine from ProtoREPL )

👍 6

cooooool ... in our next release of I will add a atom-chlorine setup as alternative to atom-protorepl 🙂 Which other atom plugins are u using for your clojure development?


#chlorine I gave a try to Chlorine 0.0.4 then 0.0.5 then 0.0.6 and still getting errors when trying to refresh the namespaces.



Failed to refresh
{:ex #error {:via [{:type clojure.lang.Compiler$CompilerException, :message "Syntax error compiling var at (unrepl-reader-703:3:117).", :data {:clojure.error/phase :compile-syntax-check, :clojure.error/line 3, :clojure.error/column 117, :clojure.error/source "unrepl-reader-703", :clojure.error/symbol var}, :at [clojure.lang.Compiler analyzeSeq "" 7114]} {:type java.lang.RuntimeException, :message "Unable to resolve var: clojure.test/*load-tests* in this context", :at [clojure.lang.Util runtimeException "" 221]}], :trace [[clojure.lang.Util runtimeException "" 221] [clojure.lang.Compiler$TheVarExpr$Parser parse "" 720] [clojure.lang.Compiler analyzeSeq "" 7106] [clojure.lang.Compiler analyze "" 6789] [clojure.lang.Compiler analyze "" 6745] [clojure.lang.Compiler$InvokeExpr parse "" 3888] [clojure.lang.Compiler analyzeSeq "" 7108] [clojure.lang.Compiler analyze {:repl-tooling/... (unrepl.repl$JheDmiOxCQTNBrUuDsZnDvb59lc/fetch :G__1284)}] {:repl-tooling/... (unrepl.repl$JheDmiOxCQTNBrUuDsZnDvb59lc/fetch :G__1285)}], {:repl-tooling/... nil} {:repl-tooling/... (unrepl.repl$JheDmiOxCQTNBrUuDsZnDvb59lc/fetch :G__1286)}}, {:repl-tooling/... nil} {:repl-tooling/... (unrepl.repl$JheDmiOxCQTNBrUuDsZnDvb59lc/fetch :G__1287)}}


@U3K24G7C5 Turn off that option. I have the "simple" (just :reload) option selected and have it set to not refresh on save.


I've always found auto-refreshing in editors to be a giant pain and I always turn it off.


And please take this to #chlorine -- as requested in the announcement!


Thanks @U04V70XH6 I will try the “simple” reload option


Publishing a Clojure getting started type article/tutorial soon. I take a pretty unusual approach. It's windows focused so would especially appreciate windows users trying it. All feedback appreciated, thank you!

👍 4

Published on Thanks for the feedback on github and couple of stars.