aerial.nvim VS dap-buddy.nvim

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

There was also https://github.com/Pocco81/dap-buddy.nvim, but it's broken since some point and no longer maintained

Not a packer based solution, but you could also add something like this Makefile to set the runtime path at the plug-in's git root. This way you could just run make and test your plugin easily.

See https://github.com/Pocco81/dap-buddy.nvim/issues/71. The migration is uncomplete but the author didn't use a dev branch or something, so I'd recommend you pin at 24923c3 which is the latest version before the unexpected change.