.config VS nvim-lazyman

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.

I made Github Pages from some of my repositories. It's a nice feature, thanks!

$NVIM_APPNAME might help if the distro's file structure doesn't work with your git model (like, AstroNvim wants you to use a sub-theme-thing for your personal config customizations, and this might not be graceful to implement as just a separate git branch). https://gist.github.com/elijahmanor/b279553c0132bfad7eae23e34ceb593b has some shell functions using nvim_appname for easily switching between different config repos and even https://github.com/doctorfree/nvim-lazyman for trying out different distros.

I haven't posted much about lazyman because I'm busy working on it and it is changing rapidly. Also, as you can see, a lot of my time is spent dreaming up Neovim configuration management fantasies.

There are many excellent distributions, personal configurations, and custom configurations to study. I wrote a Neovim configuration manager to make it easy for me to install, initialize, and explore multiple Neovim configurations. Most of the popular Neovim distributions and configurations are supported in this tool.

I'm also a fan of these preconfigured Neovim configurations. I've learned a lot by exploring many of them. To help me install and initialize multiple Neovim configurations I wrote Lazyman, a Neovim configuration manager. Currently Lazyman supports over 40 Neovim configurations.

This one has a good collection of configs, from simple to complicated: doctorfree/nvim-lazyman

See https://github.com/doctorfree/nvim-lazyman for info on Lazyman.

Currently lazyman supports Neovim configurations using the Lazy, Packer, and vim-plug plugin managers. Not all Neovim configurations install and initialize cleanly. Some have hard-coded paths assuming ~/.config/nvim as the configuration location. Others do not initialize cleanly from the command line (nvim --headless ...). However, many configurations not supported out-of-the-box by lazyman can be installed and initialized. If you find an interesting configuration that works well with Lazyman or if your favorite config does not initialize cleanly with Lazyman then open an issue at https://github.com/doctorfree/nvim-lazyman/issues