This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-09-15
Channels
- # announcements (71)
- # architecture (2)
- # aws (41)
- # babashka (23)
- # beginners (80)
- # calva (26)
- # chlorine-clover (11)
- # cljfx (4)
- # cljs-dev (12)
- # clojure (78)
- # clojure-berlin (5)
- # clojure-czech (3)
- # clojure-dev (9)
- # clojure-europe (45)
- # clojure-france (16)
- # clojure-gamedev (2)
- # clojure-italy (3)
- # clojure-nl (4)
- # clojure-spec (8)
- # clojure-sweden (1)
- # clojure-uk (37)
- # clojurescript (18)
- # community-development (15)
- # conjure (30)
- # cursive (51)
- # datomic (16)
- # duct (19)
- # figwheel-main (3)
- # fulcro (23)
- # java (7)
- # jobs (2)
- # joker (10)
- # off-topic (7)
- # parinfer (1)
- # pathom (6)
- # reagent (5)
- # reitit (1)
- # remote-jobs (1)
- # sci (1)
- # shadow-cljs (55)
- # slack-help (3)
- # specter (4)
- # sql (21)
- # tools-deps (11)
- # vim (5)
- # xtdb (14)
does “structural selection in let” mean semantic highlighting in ah, never mind. it’s what i thought it is, which is awesome! 🎉 i noticed the github issue has a comment that has a request for the same behavior for map literals. will this work there as well?let
binding vector?
> When extending selection in maps or let-binding or similar forms (e.g. cond, assoc pairs etc) the pairs of forms will now be selected as an intermediate step. Nice!!
as a heavy user of “extend/shrink selection”, this is a huge quality of life improvement! thanks!
Just asking is this even possible in IDEA/Cursive (not implemented yet, I'm aware) - to customize IDEA to pretty print various content types (say application/edn) in HTTP responses.... Currently JSON gets pretty printed, but EDN not:
GET
HTTP/1.1 400 Bad Request
Date: Tue, 15 Sep 2020 05:57:27 GMT
Content-Type: application/edn; charset=utf-8
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: *
Access-Control-Allow-Headers: *
Content-Length: 456
Server: Jetty(9.4.28.v20200408)
{:spec "(spec-tools.core/spec {:spec (clojure.spec.alpha/keys :req-un [:spec$6285/s1 :spec$6285/s2]), :type :map, :leaf? false})", :problems [{:path [:s2], :pred "(clojure.core/fn [%] (clojure.core/re-matches #\"[a-z]*\" %))", :val "worldz123", :via [:spec$6285/s2 :my-clojure-demo.api/only-small-letters-spec], :in [:s2]}], :type :reitit.coercion/request-coercion, :coercion :spec, :value {:s1 "abcorldwbh", :s2 "worldz123"}, :in [:request :query-params]}
I find using IDEA's HTTP request support nice - similar to curl/httpie/postman, probably weaker than some, but nice to have everything in one place, no context switching
@cfleming has the matching paren highlighting changed? I've upgraded from a goodness-knows-how-old version of cursive to the latest, and keep hitting newline on the wrong paren now - it's like it used to match on the paren before the caret, and now it highlights based on the current paren?
@U050CLJ53 Can you show a screenshot of what you mean? I’m not seeing what I think you mean here, but I might be wrong.
So, in this case, I (think I) expected the highlight on the paren by the +
instead of fn
the only reason I noticed this is because I'm suddenly getting it wrong very consistently
Maybe, I’ve never used the block caret, so it’s not clear to me exactly where the caret is. I would assume that screenshot is the equivalent of having the caret before the final paren, but you’re right that that highlighting makes it look like it’s after it.
ye, the actual 'position' of the caret on block caret is to the left of the block - I assumed this was just a display thing :rolling_on_the_floor_laughing:
After updating cursive a few minutes ago, datomic stuff looks a little weirder (i have generated stubs):
although i can imagine that those things can't be resolved by cursive, it makes all my queries look like something is wrong
After updating to the latest Cursive (1.9.4-eap4-2020.2), my monorepo style project will continuously ask me to generate stubs for a project. It appears to want to generate stubs for many of the modules in this project. If I keep clicking "Generate now," it'll eventually stop asking. It seems like instead it should ask me to generate stubs for all projects.
Also, after updating to the latest, all (def
s in a comment block are now marked as cannot be resolved. Example in the below screenshot.
Applying Cursive's auto-format will move the commented out datomic.client.api require too far to the left. Previously it would keep it indented to align with the first datomic.client.api require.
At some point Cursive changed how Parinfer works w.r.t. to opening a new form. It used to be the case that opening a new parenthesis would add a matching paren at the end of the parent form, e.g., given:
(+ 1 2 3)
If I were to add an opening paren right before 1 I'd get:
(+ (1 2 3))
But at some point the behavior became this:
(+ () 1 2 3)
Is this configurable? I found the former behavior nicer bc if I did want a closing paren anywhere but the end of the current parent form I'd just explicitly place one (and it'd move).Yes, I think I’ll need to make this configurable. I’ll do that for the next release.
Thanks– in the meantime, is it something I can change in a config file or something?
perfect.