.dotfiles VS kickstart.nvim

My configuration was inspired by several great sources, including lazyvim starter, ThePrimeagen’s dotfiles, kickstart.nvim, and Typecraft’s Rails config. These provided a strong foundation that I’ve adapted to fit my workflow.

https://github.com/nvim-lua/kickstart.nvim single file config in lua with the essentials. Some of the article still rings true though.

Word of caution though, if you are a tinker like me you might want to stay away from vim (or VS Code plugins) or you might lose a month of learning time as you configure everything. I mean I did deep learn my editor and lua so I cannot complain too much. If you want to still use vim or neovim then use kickstart for vim and leave the configuring alone for now.

I believe that the Neovim Kickstart project gives you Telescope as the fuzzy finder. (The YouTube video by TJ is linked in the README.)

https://github.com/nvim-lua/kickstart.nvim

Since you asked so nicely, sure. Here are the volar and ts_ls server configs for nvim-lspconfig. If you're using something like kickstart.nvim, you'll want to add these entries to your servers table:

git clone https://github.com/nvim-lua/kickstart.nvim.git $env:LOCALAPPDATA\nvim\

For casual users like me, I find Kickstart (https://github.com/nvim-lua/kickstart.nvim) a good and sensible default that's not too opinionated.

With all of the above as the foundation for my move, where did I start? Honestly, not quite at the bottom but pretty close to it with TJ DeVries' KickStart project. I went down the path of wanting to understand exactly how my setup is working and only add in the plugins that I wanted. Looking back, I just didn't have the time to fully understand exactly what this meant. However, the act of failing with KickStart did give me some solid background in how Neovim, Lua, and Lazy (the plugin manager) work.

And I did give it some time when I tried it again after a while. I would say, using kickstart.nvim was one of the best choices I've ever taken. Hat's off to TJ for creating this wonderful piece of neovim config. It slowly eased me into the world of modal editing and, thereby, into neovim.

I started by looking at The Primeagen Neovim tutorial that is only 4 videos long, used vim motions in VS Code for about a week, and then I made the jump to the real deal, I downloaded the kickstart.nvim files and starting using it. It was painful, I could not get some basic features for my personal projects working, highlight was broken as well as the go-to definitions, but as you should do as a developer, I looked up in google how to solve some issues, I found that I was missing some dependencies and I needed to install some stuff so treesitter could color my vue files, installed some LSPs, so I could write some basic Golang and I became to be productive.