evil-textobj-tree-sitter VS nvim-gps

You may be aware but the author of TFA also has a tree-sitter based minor mode called Combobulate for exactly that:

https://www.masteringemacs.org/article/combobulate-structure...

There is also evil-textobj-tree-sitter for tree-sitter based text objects for Evil mode:

https://github.com/meain/evil-textobj-tree-sitter

here are the structural editing tools, and they're great - https://github.com/meain/evil-textobj-tree-sitter

evil-mode users already have options, and there seems to be a new package with general applicability too.

evil-textobj-tree-sitter: provides new textobjects to evil-mode, thanks to treesitter

I have a package which lets you target language level constructs like functions, classes, conditionals etc for text objects using tree-sitter. This is specific to evil mode as of now, though making it work outside evil would not be that big an effort. https://github.com/meain/evil-textobj-tree-sitter

Other than combobulate, these packages also use tree-sitter for changing code (not just highlighting): * https://codeberg.org/FelipeLema/tree-sitter-indent.el * https://github.com/meain/evil-textobj-tree-sitter

this might interest you: https://github.com/meain/evil-textobj-tree-sitter

not lsp, treesitter is the way to go. lsp does not provide AST ATM. There is already https://github.com/meain/evil-textobj-tree-sitter . As a side note, smartparens work on non-lispy code. I am very happy with using in combination with evil-cleverparens.

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