How do I disable mini.indentline in the dashboard

[cjnucette]

I am trying the following:

vim.api.nvim_create_autocmd('Filetype', {
	desc = "Disable mini.indentline by filetype",
	group = vim.api.nvim_create_augroup('disable-miniindentline', { clear = true }),
	pattern = { 'snacks_dashboard' },
	callback = function(args)
		vim.b[args.buf].miniindentscope_disable = true
	end
})

but the pattern doesn't seem to match.

[tsakirist]

I want to disable other plugins as well there but it seems that the filetype="snacks_dashboard" is not emitted when initially started. If you open it manually with Snacks.dashboard.open() the event is emitted and the aucmds work.

[dpetka2001]

If you're using lazy.nvim just lazy-load mini.indentscope in event = BufReadPost or something. Then it shouldn't be loaded in Snacks dashboard on startup.

[tsakirist]

That's what I've done for that already, albeit not ideal. There could be cases where one might need the ft (?) so if my assumption is correct and the ft is not emitted initially could be problematic.

[cjnucette]

@dpetka2001 Thanks for the suggestion, but I would rather see this fixed.

[dpetka2001]

It's not about the filetype being emitted or not. Snacks dashboard loads immediately at startup and the problem is that the FileType event from Neovim does not get fired until afterwards. So, the autocmd on FileType doesn't get evaluated on startup. FileType event usually happens after a buffer is read. It's a matter of how Neovim events happen and trigger.

[dpetka2001]

@cjnucette I don't believe there's anything to be fixed since Neovim itself does not trigger the FileType event until afterwards. I have the following script in my dotfiles (which I borrowed either from here or here). I put that script in ~/.config/nvim/plugin/log-autocmds.vim in my personal configuration.

Then just run nvim -c "LogAutocmds" and after exiting Neovim rename /tmp/vim_log_autocommands to /tmp/vim_log_autocommands_no_file. Then run again nvim -c "LogAutocmds" and press s to restore a session and exit again. Neovim will feel a little sluggish during these steps because of the logging of the events happening in the background. If you then diff /tmp/vim_log_autocommands with /tmp/vim_log_autocommands_no_file you will see that in the file /tmp/vim_log_autocommands_no_file no FileType event has been triggered.

It's just the way Neovim triggers different events in different order. When dashboards load at startup, the FileType event has not yet been triggered by Neovim, so autocmds which happen on FileType won't get evaluated. FileType happens after BufReadPre which happens just before a file is read into the buffer.

[infinite-ops]

I did this which looks to work for me

vim.api.nvim_create_autocmd("User", {
  pattern = "SnacksDashboardOpened",
  callback = function(data)
    vim.b[data.buf].miniindentscope_disable = true
  end,
})

[dpetka2001]

Yes, that's the way. You have to use snacks dashboard's internal events, since FileType won't get triggered at startup. Still the same can be achieved by simply lazy-loading the plugin. I don't understand the difference to be honest.

[cjnucette]

@infinite-ops That is it. Thanks.

[geodimm]

A bit late to the party but if you're using lazy.nvim as a plugin manager you can also do

{
  'folke/snacks.nvim',
  init = function()
    vim.b.miniindentscope_disable = true
  end,
  opts = {
  }
}

This is exactly what the init function is useful for as per the spec: https://lazy.folke.io/spec#spec-setup