[vim/vim] TabClosedPre may be triggered twice for same tab page (PR #19211)

3 views
Skip to first unread message

zeertzjq

unread,
Jan 18, 2026, 8:19:01 PMJan 18
to vim/vim, Subscribed

Problem: TabClosedPre may be triggered twice for same tab page when
closing another tab page in BufWinLeave (after 9.1.1211).
Solution: Store whether TabClosedPre was triggered in tabpage_T.


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

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

Commit Summary

  • 42fdd5c TabClosedPre may be triggered twice for same tab page

File Changes

(5 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/19211@github.com>

zeertzjq

unread,
Jan 18, 2026, 8:57:04 PMJan 18
to vim/vim, Push

@zeertzjq pushed 1 commit.

  • 31a1586 TabClosedPre may be triggered twice for same tab page


View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/19211/before/42fdd5cf7d9bae909c2aee412b08549fe700f754/after/31a1586bfa700471807ce6b78b14e900a7118b46@github.com>

zeertzjq

unread,
Jan 18, 2026, 9:08:17 PMJan 18
to vim/vim, Push

@zeertzjq pushed 1 commit.

  • cfe7b43 TabClosedPre may be triggered twice for the same tab page

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/19211/before/f6aa23e5c5d49f47ede8b1083e94ea19b63d5426/after/cfe7b43235f79118f609d8faa56503c83f3229c8@github.com>

Christian Brabandt

unread,
Jan 19, 2026, 2:01:26 PMJan 19
to vim/vim, Subscribed
chrisbra left a comment (vim/vim#19211)

thanks


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/19211/c3769729807@github.com>

Christian Brabandt

unread,
Jan 19, 2026, 2:01:38 PMJan 19
to vim/vim, Subscribed

Closed #19211 via 9168a04.


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/19211/issue_event/22145290135@github.com>

Reply all
Reply to author
Forward
0 new messages