This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-02-16
Channels
- # announcements (7)
- # asami (31)
- # aws (9)
- # babashka (29)
- # bangalore-clj (8)
- # beginners (153)
- # calva (4)
- # cider (21)
- # clj-kondo (29)
- # clojure (78)
- # clojure-australia (2)
- # clojure-dev (63)
- # clojure-europe (22)
- # clojure-italy (7)
- # clojure-nl (3)
- # clojure-norway (4)
- # clojure-uk (25)
- # core-async (1)
- # cursive (24)
- # datomic (33)
- # emacs (15)
- # events (2)
- # fulcro (4)
- # girouette (1)
- # google-cloud (2)
- # graphql (14)
- # honeysql (15)
- # instaparse (1)
- # jobs (2)
- # jobs-discuss (2)
- # meander (18)
- # off-topic (100)
- # pathom (48)
- # pedestal (2)
- # polylith (5)
- # practicalli (4)
- # reveal (8)
- # shadow-cljs (3)
- # spacemacs (12)
- # sql (23)
- # tools-deps (1)
- # uncomplicate (1)
- # vim (21)
- # xtdb (19)
@dev964, you make me wonder what it means?
seems that NeoVim 0.5 release is near
from what I remember their previous releases were around Christmas
@clojurians-slack100 Sorry to say but I gave up on these aligned things, they seem nice at the beginning but make diffs hard to read and generally a PITA 😞

maybe people think of them as two column tables?
I mean, I always put two per line, because they do pair up with left and right having distinct meanings
^That's exactly how I think of them. I like seeing keys on the left and values on the right.
It's undoubtedly easier to read when they're aligned. Especially in destructuring let
binding blocks (and similar). But @orestis is 💯 % correct about the practical problems with doing so.
I'm in the habit of reviewing git diffs with the -w
flag to ignore lines where the only change is whitespace, and on GitHub with the ?w=1
query param which does the same thing. Once you know how to do that, it's easy to filter out the noise that comes with aggressive whitespace adjustments.