[vim/vim] Patch 9.1.1757 causes issue on ubuntu/wayland with some terminals (foot, urxvt, zutty) (Issue #18297)

[gcanat]

gcanat created an issue (vim/vim#18297)

Steps to reproduce

echo "set background=dark" > test.vim
vim --clean -u test.vim

Observe error message showing up when using Wayland with foot or urxvt terminal (also with zutty terminal).
No error when using kitty terminal.

Expected behaviour

No error message

Version of Vim

9.1.1757

Environment

OS: Ubuntu 24.04 (Wayland)
Terminal: foot or urxvt or zutty

Logs and stack traces

Error detected while processing TermResponseAll Autocommands for "osc":
E46: Cannot change read-only variable "v:termrbgresp"
E46: Cannot change read-only variable "v:termrfgresp"

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

[Christian Brabandt]

chrisbra left a comment (vim/vim#18297)

That patch should have removed the colorresp plugin. Do you still have it?

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

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/18297/3289878273@github.com>

[gcanat]

Closed #18297 as completed.

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

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issue/18297/issue_event/19688393081@github.com>

[gcanat]

gcanat left a comment (vim/vim#18297)

Ok yeah, I still had it /usr/local/share/vim/vim91/plugin. I removed the file and the error is gone.
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/issues/18297/3289939794@github.com>

[Jason Bowen]

jwbowen left a comment (vim/vim#18297)

I still have the plugin when compiling from 115b533. I had to manually sudo rm -v /usr/local/share/vim/vim91/plugin/colorresp.vim to be able to launch vim without the errors.

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

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/18297/3300595461@github.com>

[Maxim Kim]

habamax left a comment (vim/vim#18297)

I still have the plugin when compiling from 115b533. I had to manually sudo rm -v /usr/local/share/vim/vim91/plugin/colorresp.vim to be able to launch vim without the errors.

Or you could uninstall vim and then install it:

$ sudo make uninstall
$ sudo make install

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

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/18297/3300633500@github.com>

[Jason Bowen]

jwbowen left a comment (vim/vim#18297)

@habamax it's literally never occurred to me to attempt to uninstall vim(1) in any way for any reason. But good point, lol, and thank you. It makes me happy to have something cleaner than sudo rm in the issue thread.

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

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/18297/3303309864@github.com>

[Shane-XB-Qian]

Shane-XB-Qian left a comment (vim/vim#18297)

It happened before, some kinds of the reason of why we should better reduce the duration of backout,
maximal 1 week like i said in another ticket recently (about the dev 'policy' about 'preinsert' hl),
otherwise some mess like this may happen.

--
shane.xb.qian

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

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/18297/3303517537@github.com>