nvim-lua VS kickstart.nvim

I recently converted vim-tmux-navigator to lua via a simple function and using A-hjkl\ binds (which has no conflicts) instead of the default C-hjkl\, feel free to reuse my code, relevant commit.

source: https://github.com/ibhagwan/nvim-lua/blob/main/lua/lsp/rename.lua

I guess this is a preference thing, I would consider my config my config highly customized and pretty advanced, it has almost 8k lines of code, I don't fiddle with it as much as when I just converted to lua but I still update ocasionally and I find lua perfect for the job, instead of macros I just create small lua functions in order to avoid code duplication (where applicable).

I'm not just giving you complements to boost your morale, I've seen your code first hand, I've used feline (we even interacted in issues) and also copied your archived nvim-reload code into my config and can recognize a good programmer when I see one.

Technically all you need to do is set package.loaded[module] = nil for all the modules you wish to reload and that's why my modded version does, it reloads all your entire neovim config and all the plugins listed in the linked init file.

FYI, just added this to my config with a slight twist (resize back once I'm done), this so great :)

My config isn’t a “permade”, it’s not meant to be a solution for anyone other than myself, nevertheless you might find it useful for plugin selection and some cool functions.

You can view my setup here.

My own version of Embark colorscheme and feline.nvim, my configuration can be found here

Btw, if anyone wants the “evil-line” equivalent config for feline you can find it here

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.