Fork me on GitHub

and clj-refactor is a big ball of hacks by the looks of it 😞


@channel: We have just applied for Clojurists Together funding! We have had some great traction with @mseddon’s work in blessing Calva with a much better REPL UI/Ux and want to speed up/secure its implementation.

🎉 40

Thanks for pushing for this, @orestis!


Great to hear @pez! The stuff you’re doing with Calva is super important for the Clojure community.

❤️ 15

For some reason today I became very aware that vscode highlights the rightmost rather than the leftmost paren between the cursor, and that actually started confusing me trying to close up parens if I'm not paying attention. I know @lspector mentioned this. I wonder if other people feel strongly either way? A simple highlighter can probably be added to aid this, but it would also require turning off the 'default' paren matching while editing clojure files, to avoid noise.


@mseddon I’m not sure I understand? Have a pic?


The issue I have is after I close a paren, I don't have feedback about the paren I just closed, when there is a different paren in front of the cursor.


vscode prefers to match the paren to the right of the cursor, whereas emacs for example always highlights the paren to the left. (because the 'cursor' is not an i-bar, it is a block cursor at the point, so it is unambiguously on a particular character, not between two)


it's not something I have noticed before, but it's started to get me, after using emacs for a while.


this is quite a bike-shedding issue, of course, hence my query


what I want, always.


what vscode randomly gives me if there's a paren directly in front of the cursor.


and of course, this situation arises often, because vscode auto-inserts a close paren immediately, and then overtypes it.


Ahh I get you. I’m sure I have run into this a few times.