fix(statuscol-nvim): flickring when statuscol width is not default

[meijieru]

📑 Description

When the status column has a non-default width, alpha-nvim may shift, leading to flickering.
This pull request addresses the issue and enhances performance.

An example configuration is provided.

{
    "statuscol.nvim",
    opts = function(_, _)
      local builtin = require "statuscol.builtin"
      local opts = {
        setopt = true,
        -- https://github.com/luukvbaal/statuscol.nvim/issues/72#issuecomment-1593828496
        ft_ignore = { "Overseer*" },
        bt_ignore = { "nofile", "prompt" },
        segments = {
          {
            sign = { name = { "GitSigns" }, maxwidth = 1, colwidth = 1, auto = false },
            click = "v:lua.ScSa",
          },
          {
            text = { builtin.lnumfunc, " " },
            condition = { true, builtin.not_empty },
            click = "v:lua.ScLa",
          },
          {
            sign = { name = { ".*" }, maxwidth = 1, colwidth = 1, auto = false },
            click = "v:lua.ScSa",
          },
          { text = { builtin.foldfunc, " " }, click = "v:lua.ScFa" },
        },
      }
      return opts
    end,
  }

ℹ Additional Information

[github-actions]

Review Checklist

Does this PR follow the [Contribution Guidelines](development guidelines)? Following is a partial checklist:

Proper conventional commit scoping:

• If you are adding a new plugin, the scope would be the name of the category it is being added into. ex. feat(utility): added noice.nvim plugin

• If you are modifying a pre-existing plugin or pack, the scope would be the name of the plugin folder. ex. fix(noice-nvim): fix LSP handler error

• Pull request title has the appropriate conventional commit type and scope where the scope is the name of the pre-existing directory in the project as described above

• README is properly formatted and uses fenced in links with <url> unless they are inside a [title](url)

• Proper usage of opts table rather than setting things up with the config function.

[Uzaaft]

How does this enhance performance?

[meijieru]

By delaying the loading into User AstroFile event

[Uzaaft]

I don't understand why this is here. You're checking of neovim was opened with a file, but User AstroFile does that itself.

[Uzaaft]

If you want to load the plugin if the filename is empty, I'd just swap the event out instead of having this lazy = vim.fn.... thing

[Uzaaft]

Closing this