[vim/vim] Finalize listener_add() and provide a easy to use solution for plugin author need to track buffer changes incrementally (Issue #20809)

1 view

Skip to first unread message

qeatzy

unread,

Jul 21, 2026, 8:51:32 PM (9 hours ago) Jul 21

to vim/vim, Subscribed

qeatzy created an issue (vim/vim#20809)

Since listener_add() was introduced, there are many issues about it. It seems there are many mis-understanding and misconception about it, and there are many failed (broken) attempts to workaround corner-cases due to mis-understanding.

Here I will propose we take a approach to solve all problems with listener_add(), free the contributors and community from all the burdens incurred by listener_add(), and decrease the mental cost for related plugin authors, eg, lsp/linter/treesitter/completion engine writers.

There are several goal this issue try to solve

test extensively to guarantee 100% correctness of listener_add()
provide a reliable and easy to use interface provide incrementally build a copy of buffer being actively edited
optimize listener performance further

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.

h_east

unread,

12:57 AM (5 hours ago) 12:57 AM

to vim/vim, Subscribed

h-east left a comment (vim/vim#20809)

Could you point out the specific bug you're experiencing?
Feel free to provide the reproduction steps here, or just link to the issue on the plugin repository.