nvim-gps VS NvChad

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

NvChad

If you use Android device, you can try Termux , and in Termux I recommend NavChad as IDE . You can also find a lot of other useful packages .

git clone https://github.com/NvChad/NvChad $HOME\AppData\Local\nvim --depth 1 && nvim # if the above path doesnt work, try any of these paths : %LOCALAPPDATA%\nvim %USERPROFILE%AppDataLocal\nvim C:Users%USERNAME%AppDataLocal\nvim

line 1: you would have to copy it and remove all the nvchad keymaps and additionally reformat your keymaps to adopt this format. for example, if you copied the file in the link to lua/user/mappings.lua I believe you can just replace the first line with:

I'm confused as to why this is happenening as I have been able to load LunarVim and NvChad with any problems whatsoever.

I would suggest to start getting into vim by first trying out popular vim keybinding plugins available on your favorite code editor and get used to those first. Then, if you want to dive deeper into the power of Neovim, try out popular configs like LazyVim, LunarVim, NvChad... Taking Neovim from a mere text editor to a full-featured IDE with features like intellisense, debugging, testing, etc... on your own takes quite a lot of work and configuration.