dot VS kickstart.nvim

I add more stuff on top of LazyVim. See my dots here https://github.com/folke/dot/tree/master/nvim

There's some customizations I did with keyd that could be useful for others. See here

I found myself with the same problem and found a solution in LazyVim's maintainer's dotfiles. You have to configure `tsserver` like this, so it doesn't spawn multiple instances. Take a look [here](https://github.com/folke/dot/commit/aef729a076970e770ed84d817419551e82951d2c) to include it in your own configuration.

For anyone interested, I've added preliminary tailwindcss support in my dots here

Take a peek a the dotfiles of the dev who made lazy.nvim folke's dotfiles

You can see here how I added copilot to my own config (with LazyVim)

-- @ref https://github.com/folke/dot/blob/master/config/nvim/lua/util/status.lua (modified) local M = {} _G.Status = M ---@return {name:string, text:string, texthl:string}[] function M.get_signs() local buf = vim.api.nvim_win_get_buf(vim.g.statusline_winid) return vim.tbl_map(function(sign) return vim.fn.sign_getdefined(sign.name)[1] end, vim.fn.sign_getplaced(buf, { group = "*", lnum = vim.v.lnum })[1].signs) end function M.column() local diagnostic_sign, git_sign for _, s in ipairs(M.get_signs()) do if s.name:find("GitSign") then git_sign = s elseif s.name:find("Diagnostic") then diagnostic_sign = s end end local nu = " " local number = vim.api.nvim_win_get_option(vim.g.statusline_winid, "number") if number and vim.wo.relativenumber and vim.v.virtnum == 0 then nu = vim.v.relnum == 0 and vim.v.lnum or vim.v.relnum end local git_column = git_sign and ("%#" .. git_sign.texthl .. "#" .. git_sign.text .. "%*") or " " -- two spaces necessary to avoid jumping local diagnostic_column = diagnostic_sign and ("%#" .. diagnostic_sign.texthl .. "#" .. diagnostic_sign.text .. "%*") or " " -- right-aligned number column (thanks to the %=) -- %= @ref :h statusline "Separation point between alignment sections. Each section will be separated by an equal number of spaces" local number_column = "%=" .. nu local fold_column = "%C" local columns = { git_column, diagnostic_column, number_column, " ", fold_column, " ", } return table.concat(columns, "") end if vim.fn.has("nvim-0.9.0") == 1 then vim.opt.statuscolumn = [[%!v:lua.Status.column()]] end return M

I spent two weekends searching online repos about how to migrate from packer.nvim to lazy.nvim, and finally, I'm done! Big thanks to folke/lazy.nvim, folke/dot, and LazyVim!

I’m very happy with the new plugin manager lazy.nvim: 1. Powerful control over lazy loading plugins. Example: lazy load when command is run, or on certain events in neovim 2. I like how I’m able to layout the config. Each plugin I have has their own lua file for config (example from someone else dotfiles)

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.

I also suggest against using distributions. Instead of learning how to configure nvim itself you're learning to configure that specific distro.

I suggest to take someone's lua config and start from there. Kickstart.nvim is a good one: https://github.com/nvim-lua/kickstart.nvim

1) the option I wouldn’t chose, use Kickstarter. It’s a minimal starter config, using a single init.lua that helps you build a config slowly. https://github.com/nvim-lua/kickstart.nvim

I highly recommend Lazyvim for if you want to have a VSCode (ish) like experience that still exposes you to configuring in Lua. Or Kickstart.nvim if you want a more "from scratch" experience

In case it is helpful, I am using kickstart.nvim with only minor modifications.

One of the project goals is to become something like kickstart.nvim. Or, to be a reference if someone doesn't know how to do something.