nvim VS .config

Watch 'The Primeagen' neovim setup videos on YouTube to get started and look at people's nvim config to see the different ways people structure their config (e.g. https://github.com/Integralist/nvim).

https://github.com/Integralist/dotfiles (.config/nvim is a submodule to https://github.com/Integralist/nvim)

OK so I've fixed the issues I had with my config causing gopls and rust_analyzer from being overridden by mason: fix here

I've done my best to keep my config simple and sane: https://github.com/heygarrett/.config/tree/main/nvim

One option the docs don't list is using an autocommand, which is what I do because I overrule the indentation options for all file types.

I use a combination of guess-indent.nvim and :h listchars. Here's how I use them together in my config.

I even wrote my own autocmd for auto-completion, which was a lot of fun and helped me learn a lot about Neovim. Together with nvim-snippy it meets all of my needs (so far).

I'm late to the party, but I did configure my statusline without a plugin: - Screenshot - Config

I added an autocmd to make it automatic.

I learned a lot, and I created my own automated workflow for sessions that I’m quite happy about. I think the best part is it may not cover every use case I encounter, which means I get to keep learning and I get to become more familiar with a tool I use daily.

I use this in my custom statusline config, which you can see here.

This is how I currently configure my indentation. The autocmd overrides anything set by the ftplugin files during startup, and that's the easiest method I've found keep my preferences across every file type.

I think the built-in filetype plugin files are sourced after your vimrc. I got around this by adding an autocmd to re-set my indentation preferences after the ftplugins are loaded.