This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-09-25
Channels
- # announcements (10)
- # babashka (21)
- # calva (8)
- # cider (6)
- # clj-commons (5)
- # clj-kondo (37)
- # cljfx (16)
- # clojure (31)
- # clojure-australia (1)
- # clojure-europe (7)
- # conjure (8)
- # cursive (3)
- # data-science (4)
- # datalevin (6)
- # datomic (18)
- # emacs (10)
- # holy-lambda (3)
- # honeysql (4)
- # humbleui (1)
- # introduce-yourself (1)
- # lsp (13)
- # malli (6)
- # portal (8)
- # scittle (5)
- # specter (1)
- # vscode (9)
- # xtdb (5)
Maybe I'm just overlooking something/not awake yet, but am I right in thinking that babashka.curl/*defaults*
is not exposed in bb (in the built-in, that is)? Was looking to turn off compression by default on Windows (ya know, because Windows)
You're right, this is not exposed, but you could also install a newer curl which does support compression
I've asked the Windows maintainers a few times to update their outdated curl and support compression which is pretty much available everywhere
@U013JFLRFS8 Feel free to submit a PR. We could also have a function curl/disable-compression!
which alters the global var
I should probably just take away the age-old lesson: "don't rely on Windows command line tools"
well, bb.curl was built with the assumption that curl is everywhere (on people's computers)
@U013JFLRFS8 I've considered disabling compression on Windows by default, but I've never heard any complains so I just assumed that people would upgrade their system's curl
I did upgrade my curl - I think I was just a bit tunnel-visioned because I was addressing a windows issue in bbin
I've also considered try/catching
the request in case compression isn't supported where it retries the request without compression... and perhaps the detection of the curl that doesn't support compression could be cached
I’m a heavy (and grateful) user of bb for scripting.
I typically put my bb source code directly under ./script
and set my bb.edn
:paths
to ["script"]
.
This leads to bb code with single segment namespaces.
What do you think? Is that in any way a bad thing for bb scripts? Or totally fine?
My convention lately is to do the same but put the code in $project/bb
- totally random