This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # announcements (21)
- # aws (2)
- # babashka (20)
- # beginners (47)
- # bristol-clojurians (2)
- # calva (63)
- # cider (24)
- # clj-kondo (22)
- # cljs-dev (3)
- # cljsrn (6)
- # clojars (3)
- # clojure (147)
- # clojure-europe (21)
- # clojure-france (2)
- # clojure-italy (3)
- # clojure-losangeles (1)
- # clojure-nl (3)
- # clojure-spec (2)
- # clojure-uk (70)
- # clojurescript (37)
- # core-logic (6)
- # crux (9)
- # cursive (4)
- # data-science (2)
- # datomic (99)
- # events (1)
- # figwheel-main (20)
- # fulcro (26)
- # graalvm (6)
- # graphql (5)
- # kaocha (8)
- # leiningen (20)
- # meander (22)
- # nrepl (4)
- # off-topic (27)
- # pathom (5)
- # pedestal (3)
- # re-frame (20)
- # reagent (4)
- # shadow-cljs (43)
- # spacemacs (11)
- # tools-deps (55)
- # tree-sitter (6)
- # vim (8)
- # yada (14)
Hi, there! I’ve just released a new version of clj-unifier library with unified http responses. Any feedback - welcome. Link: https://github.com/just-sultanov/clj-unifier
Hi! I'd really appreciate a Rationale section in the Readme to understand what problem this tries to solve.
https://github.com/borkdude/clj-reflector-graal-java11-fix This library offers a fix for an issue that GraalVM native-image JDK11 has with clojure.lang.Reflector's use of MethodHandle. Just include it on your classpath while compiling a binary and that's it!
Calva v2.0.82 just released. It has so many updates since I last announced a change! You'll have to check the CHANGELOG for that. For this post, let it suffice with the great addition of configurable formatting of @nbardiuk's making: https://clojureverse.org/t/calva-gets-configurable-formatting/5596
excellent, excellent work on calva. lack of decent VS code clj support has been preventing me from working on clj apps more regularly. thrilled that calva is getting close to besting emacs!
Thanks. CIDER is still way ahead. It is amazing how that project has provided so much tooling that Calva can leverage. Engineering at its very finest.
the demo animated gif was meta -- took my old brain a bit to realize what was going on 🙂
i found it confusing at first, but now i am finding that it may be a nice way to get a feel for the various possibilities 👍
It's a bit like a REPL for the config. A bit mind bending to me when I first tried it. I think it will fit in well when someone needs to match some particular formatting policy.
he he -- sooner or later we'll have a machine-learning-based thing that will deduce the formatting settings 😉
I like that idea! Possibly Parinfer can be put to that use. Now I must put shackles on myself not to start trying to do it!
Just released vim-iced ver 1.1.0, Clojure Interactive Development Environment for Vim8/Neovim. https://twitter.com/uochan/status/1237852655025704960
i got socket repl completion working for something outside of the current ns (in the image
augistints.edit (`ae`) 🙂
however, i didn't have any success for the string
prep. i expected to see at least
prepend-to-defn-body show up. in the image there is a def of
prepend-to-defn-body. i got a message that ended with "Pattern not found".
should this have worked?
:IcedRequire first makes it work, ty! without doing
:IcedRequire first it doesn't seem to work (i tried again after restarting both the jvm and neovim).
nrepl automatically executes
IcedRequire when connecting, so I'll consider prepl doing too.
i've thought a bit about automatically having
IcedRequire happen upon connection. i'm not sure what it does, but perhaps it is
require? i'm not sure if socket-repl using folks would necessarily want their code loaded by default upon connection. that's not the way i'm used to anyway -- i do all of the loading manually.
may be it's obvious, but i evaluated the
ns form before trying to complete
prep. my expectation was that this should have made completion work.
in any case, i hope some of this can help with thinking about what (if anything) to do.
actually, bad expectation - i don't think evaluating the ns should do it, rather manually loading is better. sorry for any confusion :)
@ Thanks for your advice!
The initial ns on connection is usually
user, and sometimes I open a file different from the initial ns and connect.
For nrepl, vim-iced executes
IcedRequire to avoid evaluating form with unexpected ns.
It may be good to allow user selecting the behavior :)