Justin M. Keyes 436761cba2 fix(tui): late-arriving OSC11 response triggers OptionSet #40270 ...

Problem:
This test is flaky since fff9897ce3 :

    FAILED   ...Xtest_xdg_terminal/test/functional/terminal/tui_spec.lua @ 4359:
    TUI bg color does not trigger OptionSet from automatic background processing
    Expected values to be equal.
    Expected:
    { true, 0 }
    Actual:
    { true, 1 }
    stack traceback:
    ...Xtest_xdg_terminal/test/functional/terminal/tui_spec.lua:4380:
    in function <...Xtest_xdg_terminal/test/functional/terminal/tui_spec.lua:4359>

`apply_optionset_autocmd_now` does not emit `OptionSet` during startup:

    void apply_optionset_autocmd_now(...) {
      // Don't do this while starting up, failure or recursively.
      if (starting || errmsg != NULL || *get_vim_var_str(VV_OPTION_TYPE) != NUL) {
        return;
      }
      ...
    }

but if OSC 11 response arrives AFTER VimEnter, then
`nvim_set_option_value('background',…)` call triggers `OptionSet`.

Solution:
Use `:noautocmd` when setting 'background'.
Per fff9897ce3, OSC11 is not intended to trigger OptionSet.

fix https://github.com/neovim/neovim/issues/40235

2026-06-15 09:12:15 -04:00

..

nvim

fix(autoread): handle autocmd errors

2026-06-14 22:00:38 +02:00

uv

build(deps): bump luv to 1.52.1-0

2026-03-16 10:29:58 +01:00

vim

fix(tui): late-arriving OSC11 response triggers OptionSet #40270

2026-06-15 09:12:15 -04:00

coxpcall.lua

build: add luals check

2025-02-09 18:10:54 +01:00

editorconfig.lua

refactor: introduce nvim_on internally #39883

2026-05-20 17:33:01 -04:00

man.lua

docs: dev, lsp, indent-guides #39756

2026-05-14 13:13:30 -04:00