Justin M. Keyes

> Add `au BufEnter * au! BufModifiedSet` to your config to disable syncing the dirty state. We can document that. Then we don't need another setting.

Just a guess, maybe https://github.com/vscode-neovim/vscode-neovim/issues/2242 is related? Could you try using the node-client from https://github.com/neovim/node-client/pull/395 and see if that helps? Or if that's not convenient, we can just update node-client...

> only after using the VSCode Github Copilot extension, e.g. the chat window or the inline copilot pop-up That is tracked in https://github.com/vscode-neovim/vscode-neovim/issues/2184 The latest release v1.18.13 should help.

The comment just above yours links a related issue.

Fixed by https://github.com/neovim/neovim/pull/34412 in Nvim 0.12 (unreleased), and will be included in Nvim 0.11.3 maintenance release. Before commenting or reporting this issue again, confirm that you are running the latest...

Why close this? Was there a problem with it?

> The linter was upset with the use of `workspace/executeCommand`, but `client:exec_cmd` doesn't support sync operations that I can see. oh, reopen and i'll look into that

special-cased in the linter until we have a better answer: https://github.com/neovim/nvim-lspconfig/commit/8475898082ebe4ce40594a0b572be86bcc11ac45

> Consider removing netrw in favor of nothing. If somebody wants a file explorer can add a plugin. Also the tar and zip plugins. Discussed in https://github.com/neovim/neovim/issues/1507 . These plugins...

> would posit https://github.com/elihunter173/dirbuf.nvim as an alternative to dirvish if one is still looking for a plugin to replace `netrw`. > > It's small, nimble, focused, and has a nice...