is "BufRead <file>" a valid event?

[rafaeljacov]

    {
        'crates.nvim',
        for_cat = 'rust',
        event = "BufRead Cargo.toml", -- is this even valid?
        after = function ()
            require('crates').setup()
        end
    },

[BirdeeHub]

Yes.

this is correct event spec useage

    {
        'crates.nvim',
        for_cat = 'rust',
        event = "BufRead Cargo.toml",
        after = function ()
            require('crates').setup()
        end
    },

as would this

    {
        'crates.nvim',
        for_cat = 'rust',
        event = {
            { event = "BufRead", pattern = "Cargo.toml", }
        },
        after = function ()
            require('crates').setup()
        end
    },

To be honest, I thought it would fail at first glance, because when I do this in an autocommand on BufRead callback = function (e) print(vim.inspect(e)) end it says it provides an absolute path for the pattern field. I forgot that its a PATTERN and allows partial matches lol

But yes. Should be valid.

I tested it just now with

    {
        "TEST_SPEC",
        load = function(name)
            print("Hello from " .. name)
        end,
        event = {
            { event = "BufRead", pattern = "Cargo.toml" }
        }
    }

and also with

    {
        "TEST_SPEC",
        load = function(name)
            print("Hello from " .. name)
        end,
        event = "BufRead Cargo.toml",
    }

Both print when I enter a Cargo.toml file.

If you are having errors, I'm not 100% sure what it would be, do you have a message of some kind? One thing to keep in mind is that BufRead is before filetype event? Maybe it is the wrong event to load the plugin on, or vim.cmd.packadd("crates.nvim") is the wrong name idk (although I would assume you have the correct name for it because you also use nixCats which lets you see what the names should be with :NixCats pawsible)

But yeah, the easiest way to test triggers IMO is to make a fake spec which prints instead of its normal load spec (which calls vim.cmd.packadd(name)). It is a good troubleshooting technique to make sure your triggers are correct.

[rafaeljacov]

I don't have any errors, I just haven't tested it yet since I'm still currently migrating my whole config from lazy.nvim to nixCats and I haven't migrated my lsp's yet lol. Does it also work with glob patterns like "BufRead foo_*.bar"?

[BirdeeHub]

It does yes.

If you have spaces in the pattern I actually don't know, it should still be fine even then but if that were to fail, you could use the table form. But Im not sure there are any events that emit things that would have spaces in them for the pattern anyway