ssr.nvim VS oak

There is also a neovim plugin doing structural search/replace, also based on treesitter: https://github.com/cshuaimin/ssr.nvim

This is not a totally new idea. JetBrains has a well-known article to introduce Structural Search and Replace and its usage in IDEs. Unsurprisingly, NeoVim community also has a plugin called ssr.nvim. But telescope-sg integrates the power of ast-grep's structural search with our beloved fuzzy finder telescope.nvim. That's the merit I think worth a Reddit post: everything will work like Luna-watching NeoVimmers are used to!

Level 1, syntactic search and replace. The user specifies input pattern as Zig syntax with some placeholders and the desired output likewise. The compiler in parallel matches all source files and does the transformation where there is syntactic match. These days, I think this should be pretty universally available via tree sitter (https://github.com/cshuaimin/ssr.nvim) ? Still totally worth it to have first-class support.

Checkout ssr.nvim https://github.com/cshuaimin/ssr.nvim

PS: The video in the post (with Ruby's do vs {}) -- that I watched before I read what the plugin actually does -- reminded me of the structural search-and-replace plugin someone presented a while ago on this subreddit.

I'll post my own crappy one called oak which uses templates to render the result of tree-sitter queries.

https://github.com/go-go-golems/oak

I initially hope the queries would be more powerful, but they are really not. You can write queries and a resulting template in a yaml file. The program will scan a list of repositories for all these YAML files, and expose them as command line verbs.

Here is one to find go definitions:

https://github.com/go-go-golems/oak/blob/main/cmd/oak/querie...

This can then be run as:

         oak go definitions /home/manuel/code/wesen/corporate-headquarters/geppetto/pkg/cmds/cmd.go

An earth-shattering consequence of this heavenly design is that you can add repositories for various GO GO GADGETS such as sqleton, escuse-me, geppetto or oak to your projects' codebases, point to them in your config file, and BAM, you now have a rich set of CLI tools that is automatically shared across your team and kept in source control right along the rest of your code.