bigfile doesn't seem to work

[IceSentry]

I added this config

return {
  'folke/snacks.nvim',
  priority = 1000,
  lazy = false,
  ---@type snacks.Config
  opts = {
    bigfile = { enabled = true, notify = true },
    -- quickfile = { enabled = true },
    lazygit = { enabled = true },
  },
  keys = {
    {
      '<leader>gg',
      function()
        Snacks.lazygit()
      end,
      desc = 'Lazygit',
    },
  },
}

And it is correctly detected/installed by lazy and :checkhealth tells me the bigfile plugin is indeed enabled, but when I open a large file I don't see any notifications (despite the notify = true) and it still tries to enable syntax highlighting and the editor becomes essentially unresponsive.

I'm on windows 11 and I'm using neovim 0.11. I don't know if it's a bug or if I'm doing something wrong. I'm still fairly new to neovim so I'm not entirely sure how to debug this further.

[dpetka2001]

It has to do with your configuration. I'm using LazyVim and I can see the notification pop up when opening a file greater than 1.5MB. I see in your configuration that you don't have notifier enabled. Maybe that's the issue?

[IceSentry]

1. As mentioned in my question, I'm already on neovim 0.11
2. As mentioned in my question, I'm on windows, those paths don't exist. I'll try a fresh nvim tomorrow.
3. Sure, I'll try that tomorrow too.
4. Like I mentioned, even when I set the size to 0 any files I open aren't triggering bigfile it's not one specific file that is the issue.
5. I don't see why that would help, I already know opening a very large file with treesitter is slow, that's the main purpose of bigfile.

Yes a slow LSP can absolutely slow down the editor. I've had neovim become unresponsive in large rust codebases when using rust-analyzer. If the LSP server slows down the entire system then neovim will be affected. That's the other point of bigfile, to not start the LSP on big files.

Like I said in my original question, I already have all the required dependencies and :checkhealth reports everything for snacks being OK. I only mentioned dependencies because you mentioned npm.

You need to press Enter if a notification shows up, sure, but if none shows up pressing enter does nothing and like I said, the lsp and syntax highlighting are still enabled on big files or even small files if I set the size to 0. I don't need a notifier to tell me that. It would be nice to have a notification for it, sure, but it's not hard to tell it hasn't triggered.

[drowning-cat]

Do you still have the issue?

[iamxiaojianzheng]

Do you still have the issue?

Still exist

I solved it like this

-- autocmds.lua
vim.api.nvim_create_autocmd("BufReadPost", {
  pattern = "*",
  callback = function(args)
    local path = vim.api.nvim_buf_get_name(args.buf)
    local filesize = vim.fn.getfsize(path)
    if filesize > (vim.g.bigfile_size or 1024 * 1024) then
      vim.bo.filetype = "bigfile"
    end
  end,
})

[AnthonyK213]

This is a windows-specific problem, the path separator might be different here), so vim.api.nvim_buf_get_name(buf) must be normalized. Fixed in pr #1969.

[sharpchen]

I have same issue on wsl, the bigfile module is not loaded at all. It has nothing to do with path separator, vim.fn.getfsize can handle back slash itself

EDIT: it seems to be lazy.nvim problem. I have to call setup manually in config, opts wouldn't do anything.

  {
    'folke/snacks.nvim',
    priority = 1000,
    lazy = false,
    config = function()
      require('snacks').setup {
        picker = { enabled = true, ui_select = true },
        bigfile = { enabled = true, notify = true },
        quickfile = { enabled = true },
      }
    end
}