.config VS NvChad

I wrote a small shell function that does exactly that. Uses gh and yq (you can replace the yq post with jq)

https://github.com/chrisgrieser/.config/blob/main/zsh/config...

I'm also in Berlin, here is my dotfile repo info, contact, etc.

my nvim config here

Here is the file watcher setup in my config: https://github.com/chrisgrieser/.config/blob/main/nvim/lua/config/automating-nvim.lua

Neovim is my daily driver for editing code and configuration files. Combined with NvChad, it becomes a fast, modern IDE with smart defaults, LSP support, treesitter syntax highlighting, and a beautiful UI. I love how customizable it is. I can tweak everything from keybindings to themes, making it fit my exact workflow. Even though it's my secondary code editor, but No.1 in CLI.

If you're using NvChad, a modern and minimal Neovim configuration, integrating cz into your workflow can drastically improve your Git hygiene without ever leaving the comfort of your editor.

The default mappings are defined here.

lazy.nvim is the most popular plugin manager of Neovim. Typical Neovim distributions, such as LazyVim or NvChad, use lazy.nvim in base, so many users use lazy.nvim without knowing it. Here I wrote one point advice to use lazy.nvim.

After a short chat with my colleague I began with NvChad, a preconfigured setup that promised a modern UI and essential plugins. It provided a solid foundation, but the real magic happened when I started customizing it to suit my needs.

My first attempt at a distro was NvChad. NvChad is well-liked, polished, and a really good place to start. I know as of this writing, Rakesh is still flying high with NvChad and enjoys it very much. Something about it felt too proprietary though. Custom loaders, dealing with packages in certain ways, and that sort of thing. I wanted something prebuilt but felt more like KickStart in that plugin adds and configurations felt more Neovim "native".

NvChad