wildfire.vim VS aerial.nvim

I used to use https://github.com/gcmt/wildfire.vim, but now I'm more interested in the incremental_selection provided by treesitter. It seems more modern and offers a syntax-aware way of performing incremental selections. Generally, it is smarter than wildfire and allows me to use fewer keystrokes to select the desired portions.

A possibly more useful one, using Wildfire:

Is this treesitter-native support for wildfire?

For this particular problem, the wildfire plugin does most of the heavy lifting for the user, and the enter/backspace shortcuts become terribly addictive after just a few uses.

I tried aerial.nvim the other day and it's pretty cool. Haven't tried lspsaga yet so I'm not sure if it fits the same purpose.

I am using aerial found here and I really like it except that when I press a function, it doesn't close the window. And I had thought I fixed it with

I am referring to the aerial plugin found [here[(https://github.com/stevearc/aerial.nvim)

I use https://github.com/stevearc/aerial.nvim, it knows which is the current function. I currently open the telescope display and just press "enter", but AerialPrev would work just as well.

First one could be lualine and Aerial.

I also use ]m, but it’s not a very good way to choose and move to functions quickly and with intention. Options include aerial.nvim, symbols-outline.nvim, and the new nvim-navbuddy, from the developer who made nvim-navic.

This would be amazing if i could open it in a buffer beside (or under...?) my current. Something akin to aerial.nvim.

Yup! Aerial.nvim supports man pages, LSP, treesitter, and markdown for outlining

AstroNvim is using aerial.nvim which is a great code outline plugin. It has several supported backends on top of LSP and Treesitter it also supports Man page structure and Markdown structure explicitly. We also use the API for building the breadcrumbs at the top of each window as well!

https://github.com/stevearc/aerial.nvim