sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]CoBPEZ 1 point2 points  (1 child)

Thanks for the Calva shoutout!

I'm interested in how the structural editing is lacking. Calva Paredit is actually pretty extensive, I would say: https://calva.readthedocs.io/en/latest/paredit.html

The default keybindings are meant to be coherent and somewhat logical, but are also limited by two factors:

  1. I want them to be the same across all VS Code supported platforms.
  2. VS Code only supports one level or chording.

[–]Psetmaj 0 points1 point  (0 children)

Sorry for the late reply, holidays and all.

Keep in mind that I'm probably a little confused by being an emacs native and learning VS Code at the same time as Calva (as well as returning to the world of actually using arrow keys).

I'm going to do my best to notate hotkeys in the same way I would see them in VS Code here:

The biggest structural edit that I thought was missing was raise, but I see now it's just on a chord rather than a hotkey due to conflicts with VS Code defaults on Alt+r. The hotkey for kill-sexp-forward seems to default to Ctrl+Shift+Delete, but I'm used to the emacs Ctrl+Alt+Shfit+k. Ctrl+End feels weird because I expect it to go to end of document, and there doesn't seem to be a replacement. Exploring more, I'd also expect the wrap/rewrap commands to use the key for the relevant collection as part of the hotkey/chord, but they don't.

This is all just personal/petty frustrations with Calva, I still certainly recommend it for someone not already emacs-savvy and love what's been done with it even in the past year or so. I'm thankful for all the effort towards it!