diff options
| author | Justin M. Keyes <justinkz@gmail.com> | 2026-08-07 13:21:17 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2026-08-07 13:21:17 -0400 |
| commit | 0a2676e54adc4a27343fe2fce3042f97c371b06c (patch) | |
| tree | 7939e086e6eb66d2422f33ec0b0e124d7211957d /runtime/plugin/python_setup.vim | |
| parent | 59597316a60b11e0cde262a9b55b3e326a754e29 (diff) | |
| download | rneovim-0a2676e54adc4a27343fe2fce3042f97c371b06c.tar.gz rneovim-0a2676e54adc4a27343fe2fce3042f97c371b06c.tar.bz2 rneovim-0a2676e54adc4a27343fe2fce3042f97c371b06c.zip | |
fix(messages): :read starts a "bufwrite" progress #41219
Problem:
filemess() treats an empty suffix as "a buffer write is starting", but
readfile() calls it that way too. So ":read" (and ":edit", …) opens a
`nvim.bufwrite "<file>"` progress that is never completed.
Users of e.g. ghostty will see a stuck "progress" spinner.
Solution:
Only `buf_write()` starts the progress, via `filemess_progress()`.
Diffstat (limited to 'runtime/plugin/python_setup.vim')
0 files changed, 0 insertions, 0 deletions