Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Tracked file still shown as untracked after git.reload()

Geschlossen
  • Stimmt etwas nicht?
#3,366 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

@ytret arbeitet bereits daran.

Seit 18.10.2026.

  • #3367 von @ytret — offen

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
78/100
Issue-Typ
Bug
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
git, lua, neovim
Bereich
developer-experience, tooling

Rechercherichtung

Reproduce the bug by disabling filesystem_watchers, opening a temporary repository, and running require("nvim-tree.api").git.reload() after committing an untracked file. Start with the Git reload path in nvim-tree.api and the status-metadata update logic, then compare it with the full tree refresh path. Done means the tracked marker disappears after git.reload() with watchers disabled and a regression test covers that configuration.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

bug reproduced
Description

With disabled filesystem_watchers, running :lua require("nvim-tree.api").git.reload() does not update the tracked status of untracked/tracked files.

Neovim version
NVIM v0.12.6
Build type: Release
LuaJIT 2.1.1791988261
Operating system and version

macOS 15.7.9

Windows variant

No response

nvim-tree version

355bcc8

Clean room replication
vim.g.loaded_netrw = 1
vim.g.loaded_netrwPlugin = 1

vim.cmd([[set runtimepath=$VIMRUNTIME]])
vim.cmd([[set packpath=/tmp/nvt-min/site]])
local package_root = "/tmp/nvt-min/site/pack"
local install_path = package_root .. "/packer/start/packer.nvim"
local function load_plugins()
  require("packer").startup({
    {
      "wbthomason/packer.nvim",
      "nvim-tree/nvim-tree.lua",
      "nvim-tree/nvim-web-devicons",
      -- ADD PLUGINS THAT ARE _NECESSARY_ FOR REPRODUCING THE ISSUE
    },
    config = {
      package_root = package_root,
      compile_path = install_path .. "/plugin/packer_compiled.lua",
      display = { non_interactive = true },
    },
  })
end
if vim.fn.isdirectory(install_path) == 0 then
  print("Installing nvim-tree and dependencies.")
  vim.fn.system({ "git", "clone", "--depth=1", "https://github.com/wbthomason/packer.nvim", install_path })
end
load_plugins()
require("packer").sync()
vim.cmd([[autocmd User PackerComplete ++once echo "Ready!" | lua setup()]])
vim.opt.termguicolors = true
vim.opt.cursorline = true

-- MODIFY NVIM-TREE SETTINGS THAT ARE _NECESSARY_ FOR REPRODUCING THE ISSUE
_G.setup = function()
  require("nvim-tree").setup({
    filesystem_watchers = {
      enable = false,
    },
  })
end

-- UNCOMMENT this block for diagnostics issues, substituting pattern and cmd as appropriate.
-- Requires diagnostics.enable = true in setup.
--[[
vim.api.nvim_create_autocmd("FileType", {
  pattern = "lua",
  callback = function()
    vim.lsp.start {
      name = "my-luals",
      cmd = { "lua-language-server" },
      root_dir = vim.loop.cwd(),
    }
  end,
})
]]
Steps to reproduce
  1. Create a temporary repo
mkdir /tmp/repro && cd /tmp/repro && git init .
  1. Create an untracked file
touch example.txt
  1. Start nvim
nvim -nu /tmp/nvt-min.lua
  1. Open the neovim tree with :NvimTreeOpen. Note the star near 'example.txt'.
  2. Track the file in another terminal
cd /tmp/repro && git add example.txt && git commit -m "Track example.txt"
  1. Request Git refresh in neovim:
:lua require("nvim-tree.api").git.reload()
Expected behavior

The star near example.txt disappears.

Actual behavior

The star near example.txt does not disappear.

Additional info

Pressing R for full tree refresh removes the star.

Vorherrschende Sprache
Lua
Sterne
8.7k
Forks
642
Ø Merge
2 T. 4 Std.
Gemergte PRs (30 T.)
5

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus nvim-tree/nvim-tree.lua

Alle Issues in nvim-tree/nvim-tree.lua

Ähnliche Issues

Weitere Issues zu Lua

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.