Alternative to SIGWINCH on Unix: https://gist.github.com/rockorager/e695fb2924d36b2bcf1fff4a3704bd83. It is trivial to implement, and a good amount of terminals support it.
https://github.com/vim/vim/pull/19596
(7 files)
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Looking at it now, I don't think +termresponse is needed for synchronized output or this PR, as both do not use termcap. I originally added it because \033[2026;Ps$y would appear on the screen when running Vim in MSYS2. I will create another PR for this if this is the case.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Thanks. Does any terminal already support this?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Thanks. Does any terminal already support this?
ghostty
iTerm2
kitty
foot
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Thanks. So similar to the synchronized output setting, shouldn't we make those terminal settings configurable to allow users to opt-out of this feature just in case? E.g. like we need some t_XX key codes?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Thanks. So similar to the synchronized output setting, shouldn't we make those terminal settings configurable to allow users to opt-out of this feature just in case? E.g. like we need some
t_XXkey codes?
Well Neovim supports this, and they don't have any setting to configure this IIRC. However I suppose we can add a t_ option to let the user disable it (set to an empty string)
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
@64-bitman pushed 1 commit.
—
View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
@64-bitman pushed 1 commit.
You are receiving this because you are subscribed to this thread.![]()
@64-bitman pushed 1 commit.
You are receiving this because you are subscribed to this thread.![]()
@64-bitman pushed 1 commit.
You are receiving this because you are subscribed to this thread.![]()
@64-bitman pushed 1 commit.
You are receiving this because you are subscribed to this thread.![]()
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.![]()
@64-bitman pushed 1 commit.
You are receiving this because you are subscribed to this thread.![]()
@64-bitman pushed 1 commit.
You are receiving this because you are subscribed to this thread.![]()
@64-bitman pushed 1 commit.
You are receiving this because you are subscribed to this thread.![]()
@64-bitman pushed 1 commit.
You are receiving this because you are subscribed to this thread.![]()
@64-bitman pushed 1 commit.
You are receiving this because you are subscribed to this thread.![]()
Thanks
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.![]()