How to configure ignored and untracked_files options for git status?

[tiagoafpereira]

Is it possible to configure ignored and untracked_files options for git status?

I see those being parameterized in

neo-tree.nvim/lua/neo-tree/git/init.lua

Line 185 in 4d0828d

local make_git_status_cmd = function(porcelain_version, worktree_root, opts)

but I don't know how I should go about configuring them.

The reason for this is performance related.

NeoTree by default will fetch git status with the following flags:

git --no-optional-locks -C /Users/tiagoafpereira/Work/Altium/Valispace/repository/worktrees/Altium/current-work status --porcelain=v2 -z --ignored=traditional --untracked-files=all

Time it takes on the repo I'm working on: 1.04s user 5.36s system 51% cpu 12.511 total

But ideally it should be this instead:

git --no-optional-locks -C /Users/tiagoafpereira/Work/Altium/Valispace/repository/worktrees/Altium/current-work status --porcelain=v2 --ignored=no --untracked-files=normal

0.29s user 1.29s system 83% cpu 1.902 total

[cookesan]

I do not see a documented top-level setup option for those two values. In the current source they are internal options to make_git_status_cmd, which defaults to:

ignored = "traditional"
untracked_files = "normal"

and then builds:

--ignored=<value>
--untracked-files=<value>

The documented customization point that runs before the command executes is the before_git_status event. If you need this immediately, you can mutate the generated args there:

require("neo-tree").setup({
  event_handlers = {
    {
      event = "before_git_status",
      handler = function(args)
        for i, value in ipairs(args.status_args) do
          if value:match("^%-%-ignored=") then
            args.status_args[i] = "--ignored=no"
          elseif value:match("^%-%-untracked%-files=") then
            args.status_args[i] = "--untracked-files=no"
          end
        end
      end,
    },
  },
})

That is a workaround against current internals, not a stable first-class config API. If you want this as supported config, it probably needs a small feature change exposing those status args.