Has anyone figured out how to get the equivalent of emacs' aggressive-indent-mode? I've set "editor.autoIndent": "full" but that doesn't seem to be enough. For example:

(foo)
(bar)

;; slurp
(foo
 (bar))

;; barf, oh no!
(foo)
 (bar)

I'd like it to always always always auto indent no matter what I do, so it's impossible for indentation and code structure to differ

That looks like an issue with the Calva formatter. It focuses on the enclosing form, and runs into troubles at the top level. File it on GitHub, I don't think we ever did that.

funny, I recently asked how to make Calva indenting less aggressive like I'm used to in clojure-mode in emacs :)

ok! I'll make an issue

In general you can find some options here: https://calva.io/formatting/#configuration (@plexus)

btw, pez, the docs are pretty!

@plexus, to verify that I have understood the problem correctly you can try the same procedure with fully enclosed forms.

for me this is really the holy grail, paredit + aggressive-indent, makes me feel like I'm actually manipulating a syntax tree instead of a text file

@pez you mean with something around it like

(do
  (foo)
  (bar))

Yes.

I also want to have one more notch of aggressiveness of the indentation to kick in. I have this feeling it might make parinfer less missed.

I keep some paredit extras here: https://github.com/clyfe/calva-extras

On a similar note I'd like paredit.deleteBackward in the formation " <space> (|)" to delete just the parens first, and on second key press to delete the space; not both at once. Or maybe I'll get used to and will prefer the current beavior.

sorry, got called away for a second. Works fine when it's not at the top level @pez

(do
  (foo
   (bar)))

(do
  (foo)
  (bar))

Great. Then it’s not a regression at least. I’m at my computer now and could verify that as well.

> it might make parinfer less missed exactly, I always thought parinfer got it backwards. why manipulate structure via whitespace when you can just manipulate the structure and let the whitespace take care of itself (I'm aware many people will disagree with this sentiment 🙂 )

Parinfer does both, though? Especially if you are furtunate enough to be using an editor that can handle smart mode.

filed an issue https://github.com/BetterThanTomorrow/calva/issues/982

I think the Parinfer preference has a lot to do with personal, yeah, preferences. I was “forced” to think about Clojure code from te structural angle, because I learnt my first Clojure by pair programming with people who were using Emacs and shunned Parinfer. It stuck with me, even with my Python background. Paredit is my buddy. But for some it seems to be second nature (or quickly become at least) to indent their way to structure. I have a new colleague who belongs to that latter category, @anthony-galea. When we pair program I often notice that he accepts quite a lot of work to avoid Paredit. 😃

I have accepted that for some people parinfer works really well, I try to avoid getting into arguments about it, but I can't say I get it. And I strongly resist promoting parinfer for newcomers. If people figure out it works for them ok great, but it's clearly not a great fit for everyone. I've seen too many people (e.g. at clojurebridge workshops) just confuse themselves, accidentally ending up with some weird unexpected structure, and just having no clue how to come back from it.

Yep, I have seen a lot of these problems when learning clojure @plexus

I also avoid promoting Parinfer to newcomers. Of course somewhat because Calva’s auto-formatter does not play well with it, but mostly because I think Paredit is quite easy to learn and learning it helps in figuring out the structured nature of the code. But, yeah, arguing about this is boring. 😃 And, since the VS Code team does not get Parinfer either, Smartmode is not likely to become an option in this editor anytime soon.

but still I find calva very good to work with as a beginner

made even my first web project with it

The aspects I am interested in is mainly when Parinfer speeds up an operation. When I watch it being used I notice both that it is slower and that is faster than Paredit. I haven’t quite wrapped my head around it, but when I do I will try to use the understanding to make Calva editing more efficient.

I’ve commented on the issue with top level formatting. Could be interesting reading for anyone who is curious about the innards of Calva structural editing: https://github.com/BetterThanTomorrow/calva/issues/982

I think there are a lot of quite interesting things with Calva structural editing that I could write some articles about, btw. I might even start that soon. 😃

Here’s a VSIX with a fix for the ; line comment bug that hits some of you. It might also fix the issue that @agold had with auto-closing quotes. Please try it out, Calva friends.

what's the shortcut key for closing a tab in calva (ctrl w is taken)

You'll have to assign a shortcut, @kbosompem . At least until we update the Calva shortcut.

Toying with https://nextjournal.github.io/clojure-mode/ Nifty how modifier key highlights the form to be repl-sent.

Hi 👋:skin-tone-2: is it possible to define keybindings for certain repl-commands? I would like to have a keybinding that would tap> the form I’m evaluating. I noticed there is setting for calva.customREPLCommandSnippets but I think I cannot pass args to those snippets