[vim/vim] Fix restoring incorrect value of w_locked (PR #19728)

3 views
Skip to first unread message

Sean Dewar

unread,
Mar 17, 2026, 7:33:35 AM (16 hours ago) Mar 17
to vim/vim, Subscribed

Problem: w_locked can be bypassed when recursively set if not restored to its prior value.

Solution: rather than save/restore everywhere, just make it a count, like other locks.


You can view, comment on, or merge this pull request online at:

  https://github.com/vim/vim/pull/19728

Commit Summary

  • c1520f2 Fix restoring incorrect value of w_locked

File Changes

(6 files)

Patch Links:

—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/19728@github.com>

Sean Dewar

unread,
Mar 17, 2026, 8:08:48 AM (16 hours ago) Mar 17
to vim/vim, Subscribed
seandewar left a comment (vim/vim#19728)

Hmm, these failures look like another case of b_nwindows being wrong.
I don't think it's a bug in this change; looks like it uncovered something latent. 🫠

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/19728/c4074486507@github.com>

Sean Dewar

unread,
Mar 17, 2026, 3:07:19 PM (9 hours ago) Mar 17
to vim/vim, Push

@seandewar pushed 2 commits.

  • 3003a15 TODO: More places where b_locked_split isn't checked
  • a35bb5e Fix restoring incorrect value of w_locked

—
View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/19728/before/c1520f2321772e614d215df4196cef7e528f7de2/after/a35bb5ea2372101dc5c0af5d6e210276eea95644@github.com>

Sean Dewar

unread,
Mar 17, 2026, 3:08:53 PM (9 hours ago) Mar 17
to vim/vim, Subscribed
seandewar left a comment (vim/vim#19728)

I think I now know what's wrong with do_ecmd. Tests now pass on my fork, but I still need to look into things more to be completely happy...

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/19728/c4077367336@github.com>

Reply all
Reply to author
Forward
0 new messages