.config VS indent-o-matic

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.

there is indent-o-matic

I use indent-o-matic, along with these defaults:

I use https://github.com/Darazaki/indent-o-matic currently and set it with a keymap when that fails.

I do use a plugin to match the indentation of existing files (indent-o-matic), and that overrides my own indentation preferences; matching the indentation style of an existing codebase is more important than my own preferences or a language style guide. But if I'm starting a new project I stick to tabs for accessibility (unless it would cause whitespace syntax problems).

How does it compare to IndentOMatic?