diff options
| author | Willaaaaaaa <1091220123@qq.com> | 2026-03-12 02:16:35 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2026-03-11 14:16:35 -0400 |
| commit | 689a149b089095a29ef2fcfbf31137a230f28d07 (patch) | |
| tree | ff4f8bb871056ddbda1e5e329b6195fa6947f47e /runtime/syntax/python.vim | |
| parent | f168d215cfa2372c71e231f457b62b255f00a6e2 (diff) | |
| download | rneovim-689a149b089095a29ef2fcfbf31137a230f28d07.tar.gz rneovim-689a149b089095a29ef2fcfbf31137a230f28d07.tar.bz2 rneovim-689a149b089095a29ef2fcfbf31137a230f28d07.zip | |
fix(prompt): don't implicitly set 'modified' #38118
Problem:
In aec3d7915c55fc0b7dc73f6186cf0ae45d416d33 Vim changed prompt-buffers
to respect 'modified' so the termdebug plugin can "control closing the
window". But for most use-cases (REPL, shell, AI "chat", …),
prompt-buffers are in practice always "modified", and no way to "save"
them, so *implicitly* setting 'modified' is noisy and annoying.
Solution:
Don't implicitly set 'modified' when a prompt-buffer is updated.
Plugins/users can still explicitly set 'modified', which will then
trigger the "E37: No write since last change" warning.
Diffstat (limited to 'runtime/syntax/python.vim')
0 files changed, 0 insertions, 0 deletions