.config VS mini.nvim

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.

This is essentially a tagline of mini.move.

Just as the others suggested, oil.nvim solves this outta the box. I freaking love it (here my config in case ya need it). Apparently also mini.files handles this by default

You mean backwards seeking text objects? You can get those with mini.ai https://github.com/echasnovski/mini.nvim/blob/main/readmes/mini-ai.md

I would like to offer you to join me in saying late greetings to this autumn with a release of mini.nvim version 0.10.0. It is mostly about introducing three (quite feature full, dare I say) modules and minor updates of existing ones.

Last night I cleaned up all the dead code in my config and realised that mini.nvim has to be the single best plugin that I've used. I have a couple of other favourites but this collection has been so consistently good that I wanted to give some thanks to the juggernaut that is u/echasnovski! Thanks for all the work you plugin authors and core maintainers put in to make this editor what it is <3

For example: I spent a lot of time configuring file tree plugins to have the same sorting as VS Code, tweaking their icons, etc. But then I realized I barely used the file explorer at all, and now I'm super happy with the minimal approach of mini.files. I had similar experiences with other plugins that were just adding "fluff" instead of the functionality I was looking for.

Around two weeks ago I've announced the release of mini.files - a file explorer module of mini.nvim with column view navigation and "edit text to manipulate file system" design. This resulted into a great feedback from the community, much of which turned into new features.

A mini.ai textobject specification that you can use standalone