aerial.nvim VS nvim-gps

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

I've been using winbar.nvim with nvim-gps which depends on treesitter. Unfortunately it's been archived/deprecated but still works fine.

With the deprecation of nvim-gps we are left with LSP's more accurate code context parser nvim-navic or lspsaga. I however only use LSP for like 5 languages as opposed to treesitter since it's just easier to install all language parser

and nvim-navic or in this projects case it is its predecessor - nvim-gps

I currently use feline.nvim as a framework for creating my custom statusline, and before that I was using galaxyline.nvim. A feature that I would really like though is for each section of the statusline to able to dynamically resize based on the window size, and dissappear if the window gets narrow enough, based on some priority that I give them and some truncation rule. By truncation I mean that for instance a file path could get shortened by pathshorten(), the filetype indicator would only display the devicon and not the filetype name, nvim-gps would only use a depth of 1, etc... This behaviour would be defined by the user, but the framework would calculate which components to truncate in order to fit as many as possible in the priority that the user has chosen for each component.

I've added a pull request to support json https://github.com/SmiteshP/nvim-gps/pull/41