@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 š
I don't align either.
I'm misaligned š
I thought about lining up maps, but in the end, I just go with the flow
lets and maps aren't tabular data, alignment never made sense to me.
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.
Regardless, I'm in a code base where they're aligned, so my hands are tied š
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.
That's what all the IDE guys keep saying :troll:
Iām using vim fugitive for my own stuff but GitHub to review PRs :) alternative suggestions welcome!
Yeah, me too š
(Which I think is a useful tip, regardless of your philosophy on vertically aligning let
bindings, maps, etc.!)
> on GitHub with the ?w=1
query param
This is a game changer, thanks @dave! :bananadance: