nvim-gps VS nvim-treesitter-textobjects

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

I was hoping to use nvim-treesitter-textobjects to jump to the next argument via something like this:

You want to look at nvim-treesitter-textobjects. It let's you define keymaps for navigating text objects defined by treesitter and you can also use them with commands like d, c and so on.

Thank you! It looks like nvim-treesitter-textobjects is a good plugin to start with:

https://github.com/nvim-treesitter/nvim-treesitter-textobjec...

I'm aware of nvim-treesitter-textobjects and I suspect my answer lies in this plugin, but is there a way to move between root nodes that is agnostic of the node type?

Thanks! I just started using https://github.com/nvim-treesitter/nvim-treesitter-textobjects, and it works as a charm.

nvim-treesitter-textobjects

In this case, reading here is probably a good start: https://github.com/nvim-treesitter/nvim-treesitter-textobjects

Have a look at https://github.com/nvim-treesitter/nvim-treesitter-textobjects. Set up the @block.inner and @block.outer textobjects and it should work.

nvim-treesitter-textobjects lets you jump to (for instance) functions more accurately than with a regex-based approach using ]f

Or even better, one can use nvim-treesitter-textobjects. It already provides function/class selection and go-to functionality out-of-the-box.