symex.el VS puni

I also recommend symex[1]. Although it is more “locked-in” to s-expressions than other solutions (which takes some getting used to at first), I find that for me this is exactly what makes movement feel much more intuitive and editing much more precise.

The one thing I don’t like is that symex depends on so many other plugins (especially Evil, which I am trying to swap out with the more lightweight meow), but this will apparently change soon. They are also working towards support for non-Lisp languages via tree-sitter, but I don’t know how well it works.

[1]: https://github.com/drym-org/symex.el

The pilot projects (including Symex.el) are accepting financial contributions and will distribute them to sources of value including contributors and antecedent projects in a process that we all have a say in.

This is a really useful synopsis. symex has recently had TS support merged in, and apparently includes navigation and structural editing similar to its lisp-like language capabilities. I think it's still early going and I haven't tested, but may be worth a look.

Has anyone used symex.el without evil? I just learned it can be use with vanilla emacs (despite the 2nd word in its tagline). I also learned they have a tree-sitter branch which will expand its powers to many languages.

I started out using evil, but now I mostly use Symex. (Structural editing. non-lisps support wip for those sad moments you can't use lisp). For now depends on evil, but could be separated.

The purpose of this congress is to engage in the process of Dialectical Inheritance Attribution, which is a collective process by which we apply agreed-upon standards to the task of appraising and attributing the value of work done in the world. At this initial congress, there are two open source projects on the agenda to be appraised: Symex.el which is an Emacs extension, and Qi, which is a functional DSL on the Racket platform.

symex has a branch that’s been working on integrating with tree-sitter.

If you want to go nuts with structural editing you may also want to check out symex mode: https://github.com/drym-org/symex.el

It uses paredit (among others) for its low level functionality, but the vim-style modal interface allows you to manipulate the tree structure with single keystrokes in a precise and very expressive way. Keep in mind that you have to actively learn how to use it and it will feel awkward at first (similar to how vim feels for beginners), but I find the editing experience very pleasent and smooth after I got used to it.

Another thing I really like about it is that you can still switch to normal mode and it doesn’t get in your way like other plugins where I had to change my keybindings all the time because the amount of convenient shortcuts is still quite limited in the end. This modal switching to different editing contexts (or languages?) is something I feel should be explored much further.

For working with delimiters, you might want to check out Smartparens or Puni. There are many other packages like these, but those are the two I know about.

I'm guessing the way forward here for navigation is to change Emacs' built-in sexp-navigation when treesitter is available? forward-sexp, backward-up-list, down-list, raise-sexp etc do a good job in lisp environments, and they can now work everywhere. Packages that build on these (like Puni will automatically gain treesitter-awareness.

I have never used lispy, but I have used puni for a while now, and I'm pretty satisfied with it. I am not sure that it's exactly what you're looking for since it takes a more limited approacg, but it has a lot of the same features: slurping, barfing, raising, splicing etc.

For any Lisp you want paredit or any other structural editing package (I switched to puni recently because it’s more customizable and works with non-Lisp languages too). The first three days will suck hard because it’ll feel like the tools get in your way, but once you’re comfortable with it it’ll be the best thing ever.

Afaik puni uses only forward-sexp for navigating and manipulating sexps. So if you implement a forward-sexp-function that uses treesit.el it should work without any changes.