[vim/vim] feat; add 'termsync' setting (PR #19541)

Foxe Chen

unread,

Mar 1, 2026, 1:35:02 PMMar 1

to vim/vim, Subscribed

Same as Neovim's termsync option. Surprised this wasn't already added, consdering how simple it was to implement and it reduces flickering greatly for me on my machine.

Here's a before and after comparsion:

https://github.com/user-attachments/assets/fb45ab56-b3a8-491b-b589-3c818fa6cd25

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

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

Commit Summary

dcdfd82 add 'termsync' setting

File Changes

(10 files)

Patch Links:

—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.

Foxe Chen

unread,

Mar 1, 2026, 1:48:01 PMMar 1

to vim/vim, Push

@64-bitman pushed 1 commit.

18e4c8e add 'termsync' setting

—
View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.

Foxe Chen

unread,

Mar 1, 2026, 3:51:06 PMMar 1

to vim/vim, Push

@64-bitman pushed 1 commit.

0e364c7 add 'termsync' setting

—
View it on GitHub or unsubscribe.

You are receiving this because you are subscribed to this thread.

Foxe Chen

unread,

Mar 1, 2026, 4:17:34 PMMar 1

to vim/vim, Push

@64-bitman pushed 1 commit.

befd2f0 add 'termsync' setting

—
View it on GitHub or unsubscribe.

You are receiving this because you are subscribed to this thread.

Foxe Chen

unread,

Mar 1, 2026, 9:56:55 PMMar 1

to vim/vim, Push

@64-bitman pushed 1 commit.

1401cf2 add 'termsync' setting

—
View it on GitHub or unsubscribe.

You are receiving this because you are subscribed to this thread.

Foxe Chen

unread,

Mar 1, 2026, 9:58:24 PMMar 1

to vim/vim, Push

@64-bitman pushed 1 commit.

00a08c7 add 'termsync' setting

—
View it on GitHub or unsubscribe.

You are receiving this because you are subscribed to this thread.

Foxe Chen

unread,

Mar 1, 2026, 10:06:01 PMMar 1

to vim/vim, Push

@64-bitman pushed 1 commit.

4525f76 add 'termsync' setting

—
View it on GitHub or unsubscribe.

You are receiving this because you are subscribed to this thread.

Foxe Chen

unread,

Mar 1, 2026, 10:32:02 PMMar 1

to vim/vim, Push

@64-bitman pushed 1 commit.

3a012f8 add 'termsync' setting

—
View it on GitHub or unsubscribe.

You are receiving this because you are subscribed to this thread.

Foxe Chen

unread,

Mar 1, 2026, 11:23:45 PMMar 1

to vim/vim, Push

@64-bitman pushed 1 commit.

ec005a0 add 'termsync' setting

—
View it on GitHub or unsubscribe.

You are receiving this because you are subscribed to this thread.

Foxe Chen

unread,

Mar 1, 2026, 11:33:37 PMMar 1

to vim/vim, Push

@64-bitman pushed 1 commit.

f2b8654 add 'termsync' setting

—
View it on GitHub or unsubscribe.

You are receiving this because you are subscribed to this thread.

Foxe Chen

unread,

Mar 1, 2026, 11:35:24 PMMar 1

to vim/vim, Push

@64-bitman pushed 1 commit.

56aa075 add 'termsync' setting

—
View it on GitHub or unsubscribe.

You are receiving this because you are subscribed to this thread.

Foxe Chen

unread,

Mar 1, 2026, 11:37:07 PMMar 1

to vim/vim, Push

@64-bitman pushed 1 commit.

798f03b add 'termsync' setting

—
View it on GitHub or unsubscribe.

You are receiving this because you are subscribed to this thread.

Foxe Chen

unread,

Mar 1, 2026, 11:50:40 PMMar 1

to vim/vim, Push

@64-bitman pushed 1 commit.

af717ea add 'termsync' setting

—
View it on GitHub or unsubscribe.

You are receiving this because you are subscribed to this thread.

Foxe Chen

unread,

Mar 1, 2026, 11:51:28 PMMar 1

to vim/vim, Push

@64-bitman pushed 1 commit.

417d677 add 'termsync' setting

—
View it on GitHub or unsubscribe.

You are receiving this because you are subscribed to this thread.

Foxe Chen

unread,

Mar 2, 2026, 12:04:06 AMMar 2

to vim/vim, Subscribed

64-bitman left a comment (vim/vim#19541)

I found #11718 which this PR is related to, seems like bram did not get the point of something like this. However it has noticeably reduces flickering for me, so I guess there is a point.

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

You are receiving this because you are subscribed to this thread.

Foxe Chen

unread,

Mar 2, 2026, 9:09:25 AMMar 2

to vim/vim, Push

@64-bitman pushed 1 commit.

ed46538 add 'termsync' setting

—
View it on GitHub or unsubscribe.

You are receiving this because you are subscribed to this thread.

Foxe Chen

unread,

Mar 2, 2026, 9:20:02 AMMar 2

to vim/vim, Push

@64-bitman pushed 1 commit.

d589505 add 'termsync' setting

—
View it on GitHub or unsubscribe.

You are receiving this because you are subscribed to this thread.

Foxe Chen

unread,

Mar 2, 2026, 9:21:03 AMMar 2

to vim/vim, Push

@64-bitman pushed 1 commit.

af7f30f add 'termsync' setting

—
View it on GitHub or unsubscribe.

You are receiving this because you are subscribed to this thread.

Christian Brabandt

unread,

Mar 2, 2026, 1:34:25 PMMar 2

to vim/vim, Subscribed

chrisbra left a comment (vim/vim#19541)

out_str((char_u *)"\033[?2026$p");

Hm, we typically have those as t_<letter> options. Don't we need this here as well instead of hard coding this?

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

You are receiving this because you are subscribed to this thread.

Javier Jaramago Fernández

unread,

Mar 2, 2026, 3:13:53 PMMar 2

to vim/vim, Subscribed

JavierJF left a comment (vim/vim#19541)

This PR fixes the popup flickering, but does it as a side effect of the feature, also since it only does it for terminal that supports this feature, I think that having correctness back for popups without transparencies is important. So opaque popups don't require terminals with this feature to avoid rendering issues, while popups with transparencies will require it for avoiding flickering.

Due to this, I think that even with this PR, the with changes from #19534 are still required. Said this, I think it's a great feature to have 👍 .

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

Foxe Chen

unread,

Mar 2, 2026, 3:21:31 PMMar 2

to vim/vim, Subscribed

64-bitman left a comment (vim/vim#19541)

out_str((char_u *)"\033[?2026$p");

Hm, we typically have those as t_<letter> options. Don't we need this here as well instead of hard coding this?

Well it looks to me that all terminals that support synchronized output use this same escape sequence. However I think it is a good idea to add a t_ option for consistency

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

You are receiving this because you are subscribed to this thread.

Foxe Chen

unread,

Mar 2, 2026, 4:42:17 PMMar 2

to vim/vim, Push

@64-bitman pushed 1 commit.

46281ba add 'termsync' setting

—
View it on GitHub or unsubscribe.

You are receiving this because you are subscribed to this thread.

Foxe Chen

unread,

Mar 2, 2026, 4:45:21 PMMar 2

to vim/vim, Push

@64-bitman pushed 1 commit.

41d6c3c add 'termsync' setting

—
View it on GitHub or unsubscribe.

You are receiving this because you are subscribed to this thread.

Foxe Chen

unread,

Mar 2, 2026, 4:47:33 PMMar 2

to vim/vim, Push

@64-bitman pushed 1 commit.

a089f84 add 'termsync' setting

—
View it on GitHub or unsubscribe.

You are receiving this because you are subscribed to this thread.

Foxe Chen

unread,

Mar 2, 2026, 4:50:31 PMMar 2

to vim/vim, Subscribed

64-bitman left a comment (vim/vim#19541)

Okay I have made it so the escape codes to begin and end synchronized output are configurable by the user. I left the \033[?2026$p escape code hardcoded, because all terminals that support synchronized output use this, and it makes things simpler (esp. when detecting the response).

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

You are receiving this because you are subscribed to this thread.

Christian Brabandt

unread,

Mar 3, 2026, 8:03:28 AMMar 3

to vim/vim, Subscribed

chrisbra left a comment (vim/vim#19541)

Does this the same as in Neovim? If yes, I assume we cannot change the naming? Because if I hear termsync I associate this setting with :terminal. But that is not the case.
On the other hand, this is not true:

:h 'term<c-d>
'term'           'termbidi'       'termwinkey'     'termwinsize'    'termwintype'    'termencoding'   'termguicolors'  'termwinscroll'

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

You are receiving this because you are subscribed to this thread.

Foxe Chen

unread,

Mar 3, 2026, 9:04:07 AMMar 3

to vim/vim, Subscribed

64-bitman left a comment (vim/vim#19541)

Does this the same as in Neovim? If yes, I assume we cannot change the naming? Because if I hear termsync I associate this setting with :terminal. But that is not the case.

On the other hand, this is not true:
:h 'term<c-d>

'term'           'termbidi'       'termwinkey'     'termwinsize'    'termwintype'    'termencoding'   'termguicolors'  'termwinscroll'

I named it termsync because that's what it is named in Neovim. However I suppose we can change the name to something like syncout. What do you think?

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

You are receiving this because you are subscribed to this thread.

Christian Brabandt

unread,

Mar 3, 2026, 4:28:19 PMMar 3

to vim/vim, Subscribed

chrisbra left a comment (vim/vim#19541)

let's keep it the same as in Neovim

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

You are receiving this because you are subscribed to this thread.

h_east

unread,

Mar 4, 2026, 9:51:31 AMMar 4

to vim/vim, Subscribed

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

let's keep it the same as in Neovim

Yes. Since it is essentially a control for the terminal, I think the term prefix is fine.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

Foxe Chen

unread,

Mar 4, 2026, 2:04:07 PMMar 4

to vim/vim, Push

@64-bitman pushed 1 commit.

4b98383 add 'termsync' setting

—
View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.

Foxe Chen

unread,

Mar 4, 2026, 2:07:30 PMMar 4

to vim/vim, Push

@64-bitman pushed 1 commit.

8e53168 add 'termsync' setting

—
View it on GitHub or unsubscribe.

You are receiving this because you are subscribed to this thread.

Foxe Chen

unread,

Mar 4, 2026, 2:26:40 PMMar 4

to vim/vim, Subscribed

64-bitman left a comment (vim/vim#19541)

I think this is ready

—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.

Christian Brabandt

unread,

Mar 4, 2026, 4:12:51 PMMar 4

to vim/vim, Subscribed

chrisbra left a comment (vim/vim#19541)

thanks

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

You are receiving this because you are subscribed to this thread.

Christian Brabandt

unread,

Mar 4, 2026, 4:13:12 PMMar 4

to vim/vim, Subscribed

Closed #19541 via 7ba60f1.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

Reply all

Reply to author

Forward