openFile: nested write + BufWriteCmd handler can overwrite Claude's file during the acwrite step (known gap)

Aperta
  • Qualcosa non va?
#433 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
12/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
lua, neovim
Ambito
devtools

Direzione di ricerca

Start with the openFile paragraph of Side Effects in lua/claudecode/tools/README.md, then read earlier threads #408, #413 and #420 for the attempts already ruled out. The hard part is design: find a way to block writes of only the one buffer during the acwrite step without affecting other writes or prompts. Done means a documented, tested approach that keeps the E676 and E142 behaviour the issue describes.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

needs-triage

openFile can still write the user's unsaved text over the file Claude just changed, in one narrow case. This issue tracks it, because #413 and #420 only documented it.

When it happens. All three must hold:

  1. openFile runs its acwrite step for the buffer: the buffer was opened before its file existed, or 'eventignore' or 'eventignorewin' ignores FileChangedShell.
  2. A user autocommand with ++nested on BufEnter, BufWinEnter or BufLeave writes that buffer while openFile shows it.
  3. A user BufWriteCmd handler that matches the file (such as BufWriteCmd *) writes <afile>.

Without ++nested, or without a matching handler, the write fails with E676 and Claude's file stays. Before #408, Neovim stopped this write with E13.

What was tried.

  • Turning the global 'write' option off during the step (#413 first version) stopped the overwrite but made a common autocmd BufLeave * update autosave fail openFile with E142.
  • nowrite or nofile 'buftype' make 'modified' read as off, which loses unsaved text through other autocommands (#408 round 7).
  • readonly does not stop :w! and prompts with 'confirm'.
  • A BufWriteCmd guard of openFile's own runs after the user's BufWriteCmd *.

Where it is documented. lua/claudecode/tools/README.md, openFile paragraph of Side Effects.

A fix needs a way to block writes of this one buffer during the step without blocking or prompting other writes.

Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: high

Lingua principale
Lua
Stelle
3.1k
Fork
223
Merge medio
6h 47m
PR unite (30g)
93

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

  • Nessun Dockerfile né file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di coder/claudecode.nvim

Tutte le issue di coder/claudecode.nvim

Issue simili

Altre issue su Lua

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.