nvim-config VS kickstart.nvim

Check my repo while you see the whole serios of videos: https://github.com/RicardoRien/nvim-config You can start from here (Yeah, it's the author of LunarVim (christ@machine) but teaching us how to custom our own shit) Please, follow this steps: Install Neovim from source: https://www.youtube.com/watch?v=Vghglz2oR0c&t=483s (Like first 20 min, you don't have to watch all the videos) (please, we are in nvim 0.8, choose the correct brach and compile) Check this series of videos about how to order your folders and config basic stuff (But please, be aware, some things are outdate, just check Christ repo, go to the file copy and paste) https://github.com/ChristianChiarulli/nvim https://www.youtube.com/watch?v=ctH-a-1eUME Good luck.

In this file on line 11 you specify the LSP that you are configuring. You have to add "prismals"

Hi! I'm using L3MON4D3/LuaSnip as snippet engine, also Cmp-luasnip as snippet completions. This is my config: nvim-config (christ@machine old config, before it was 100% dedicated to LunarVim) So, I have a folder typescript with a file called generated.json

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.

I usually recommend new users to check out Kickstart. It contains a set of plugins and nice to haves so you don't have to discover them your self.

All plugins are in one file + has a lot of comments to help you get started.

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

Out of the box it offers almost nothing, but after 7 years of development I like that. I love the idea of customizing to my needs my IDE, so with the help of kickstart.nvim I have with 1 minute of installing and 10 extra minutes of configuration a complete IDE.

I recently started coding with Neovim using kickstart.nvim as the template for my editor configuration. I downloaded the python-lsp-server package using Mason, but I was disappointed to discover that the IntelliSense on my third party dependencies didn't work. The LSP was resolving to my global Python installation, which did not have the packages from my virtual environment (venv) installed.

First thing I did was get kickstart.nvim. I had heard it was extremely useful (and it was). It was very easy to install. I start reading through init.lua, and it told me to run :Tutor, which is almost 1,000 lines of learning how to use Neovim, to which I obviously ran that command and started reading. Obviously, it takes a bit of time to complete :Tutor, but it's well worth it. "hjkl" wasn't too hard to get used to, also repeating motions by using numbers was useful, such as using '5dd' to delete 5 lines. I highly suggest reading this file, especially since I didn't really know about the different modes, which is probably why I failed to switch the other times. You would start writing your code, then Neovim would say that it can't find that command, you would accidently type an i and then start typing, and so on, it was a nightmare. For those that don't know the modes, here is each mode and how to get between them.