This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-12-02
Channels
- # adventofcode (153)
- # announcements (29)
- # architecture (6)
- # babashka (5)
- # beginners (197)
- # calva (71)
- # clj-kondo (27)
- # cljfx (4)
- # cljs-dev (33)
- # cljsrn (1)
- # clojure (52)
- # clojure-australia (5)
- # clojure-boston (1)
- # clojure-europe (38)
- # clojure-france (1)
- # clojure-hungary (5)
- # clojure-italy (1)
- # clojure-nl (19)
- # clojure-uk (5)
- # clojurescript (12)
- # conjure (4)
- # core-async (3)
- # cursive (22)
- # datalog (70)
- # datomic (32)
- # deps-new (8)
- # emacs (79)
- # events (2)
- # fulcro (15)
- # graalvm (15)
- # leiningen (2)
- # lsp (5)
- # minecraft (1)
- # nbb (1)
- # off-topic (37)
- # polylith (11)
- # re-frame (9)
- # reagent (1)
- # reitit (3)
- # releases (1)
- # reveal (2)
- # shadow-cljs (35)
- # spacemacs (1)
- # tools-build (4)
- # tools-deps (55)
- # vim (11)
- # xtdb (6)
Good morning!
Morning ☀️
Morning! It’s not very good for me today, as I have had to revert yet another Calva release, An error report about a blocking bug arrived during my night and it looks to me like it could have to do with my Parinfer experiment leaking out to non-participants…
What you are doing for open source is amazing. It is clear you care a lot, and it shows. Bugs happen, it’s ok 😉
Thanks. I am not too floored from this. Happy I could revert it and get myself some wiggle room to figure it out. Now all I need are users who have the problem and can help me reproduce it.
@U0ETXRFEW Did you see my comment in one of the threads about this, regarding auto-complete wiping out closing parens?
It was happening sometimes before the parinfer work but it feels like it's been happening much more often since that work was added?
I have missed that comment, actually. And not seen it happen myself. There is something up with the changes supporting Parinfer, and this could have worsen. If you see it happen, can you reproduce it by using undo and then doing the same autocomplete? Could be something with how clojure-lsp and Calva interact….
Will try, yes.
go mornoding
[ yes, that's an order ]
mornoding sounds a bit like what coding in Clojure is ... adding nodes
(->> "good morning"
seq
shuffle
(apply str))
=> " mirogdonong"
You must always pause briefly before exclaiming mirogdonong
!To me, it’s meerog-donong. A meat pastie with cabbage
no morig dong!
@otfrom I've completed day 1 and day 2 in babashka: https://gist.github.com/borkdude/b5cf0e9d2d8ab7c678d88e27a3357b33
I'm gonna start tomorrow with the lad and see if we can catch up.
@borkdude You're not the only one! https://gist.github.com/ordnungswidrig/21224314590b871456cd4ccb2633ca8e AoC with babashka but pointless.
@ordnungswidrig oh, that's awesome, the input flags + threading!
I’m trying to replace all my weird bash scripting habits and jq with something more sensible 😛
I just released bb 0.6.8 which includes parse-long
from 1.11.0-alpha3, a popular function in AoC :)
I wonder if the things that made read-string
unsafe in Clojure (despite setting *read-eval*
to false
) also behave the same in bb, I suspect not
A good question.