Noob questions

[rieje]

• Are there any general settings (non-Mini-related) off the top of one's mind where they assume Mini is used and should be set differently otherwise or are all of them recommended regardless of whether Mini is used?

• Syntax is enabled by default, so isn't e.g. if vim.fn.exists('syntax_on') ~= 1 then vim.cmd('syntax enable') end and setting defaults redundant? Or is the philosophy simply that important settings might be included for reference? Same with vim.cmd('filetype plugin indent on').

• Can the author expand on why relatime (and perhaps another example of a popular setting) is not used beyond "does not provide the best user experience)? I know vim's builtin ways may be more precise but from some I usage I still think e.g. fewer keystrokes and attention might be demanded in certain circumstances, e.g. 12k <ft motions> vs. e.g. ? <search term> <nnnn>. especially if the buffer has similar words. It's obviously a subjective choice though. I'm still on the fence with plugins like leap.nvim--they are obviously not "necessary" or the "vim way" and vim navigation is a strong point, but pretty sure they let you jump to any arbitrary position on the buffer quite a bit faster without e.g. repetitive motions and/or counting (even if using / there may be similar words) at the cost of reading and entering 1-3 characters where the eyes are.

• Is there a suggested way to easily benchmark startup time of plugins to get a sense of e.g. whether a plugin is "properly" lazy-loaded? especially since vim.pack kind of assumes this and may not necessarily allow all the control lazy.nvim offers in this aspect?

• Also curious if the author's own config has any notable additions or deviations from MiniMax in terms of some aspects of the config in general or in particular since MiniMax is thoughtfully crafted for general use and as a balance between features and complexity.

I'm currently using MiniMax's config structure as a basis to build my own config but opting in to Mini plugins as opposed to opting out.

Much appreciated.

[echasnovski]

• Are there any general settings (non-Mini-related) off the top of one's mind where they assume Mini is used and should be set differently otherwise or are all of them recommended regardless of whether Mini is used?

Do you mean 'plugin/10_options.lua' file? If yes, then almost all of them are not exactly tied to MINI. They are somewhat subjective recommendation for a better default user experience. Some exceptions are maybe:

• vim.o.showmode = false assumes that there is a statusline that shows current mode. In MiniMax it is 'mini.statusline', but it can be any other one.
• Built-in completion options are good on their own, but in particular they are good for 'mini.completion'.

• Syntax is enabled by default, so isn't e.g. if vim.fn.exists('syntax_on') ~= 1 then vim.cmd('syntax enable') end and setting defaults redundant? Or is the philosophy simply that important settings might be included for reference? Same with vim.cmd('filetype plugin indent on').

It might be the case that these are redundant. I vaguely remember removing them couple of years ago and something went wrong. Probably need to look at them more carefully.

• Can the author expand on why relatime (and perhaps another example of a popular setting) is not used beyond "does not provide the best user experience)? I know vim's builtin ways may be more precise but from some I usage I still think e.g. fewer keystrokes and attention might be demanded in certain circumstances, e.g. 12k <ft motions> vs. e.g. ? <search term> <nnnn>. especially if the buffer has similar words. It's obviously a subjective choice though. I'm still on the fence with plugins like leap.nvim--they are obviously not "necessary" or the "vim way" and vim navigation is a strong point, but pretty sure they let you jump to any arbitrary position on the buffer quite a bit faster without e.g. repetitive motions and/or counting (even if using / there may be similar words) at the cost of reading and entering 1-3 characters where the eyes are.

If you mean 'relativenumber', then I think having it enabled all the time is too visually distracting. A better approach is to enable them only in Visual mode, which is what 'mini.basics' offers. But that is also a matter of preference.

I do rarely use relative numbers for jumps. Usually for "close distance" jumps, like 2j. I'd say up to 5 lines. To me other ways of jumping combined provide more usability, like:

• { / } to jump to next paragraph.
• H / M / L to jump within visible lines.
• Indeed a jumping plugin. I use 'mini.jump2d' (with better defaults that will hopefully be upstreamed soon).

• Is there a suggested way to easily benchmark startup time of plugins to get a sense of e.g. whether a plugin is "properly" lazy-loaded? especially since vim.pack kind of assumes this and may not necessarily allow all the control lazy.nvim offers in this aspect?

I think running nvim --startuptime nvim.log couple of times and explore the times is enough.

• Also curious if the author's own config has any notable additions or deviations from MiniMax in terms of some aspects of the config in general or in particular since MiniMax is thoughtfully crafted for general use and as a balance between features and complexity.

You can take a look yourself. The MiniMax is very close to what I've been daily driving for at least couple of years now.

---

Welcome to Neovim and thanks for your interest in MiniMax :)