WARNING: DSR response from terminal

[miEsMar]

Hey, It's since few days (after one of the latest pull from the upstream repo) I am seeing this warning message appearing at startup:

What does it mean?

[zeertzjq]

It means exactly what it says.

[miEsMar]

I always don't know if to laugh or cry at answers like yours honestly.
Next time better off not waste your time going around answering like this to people who genuinely ask questions to understand what is going on. I don't think most of the people neither want nor need things like this.
Let's try to put a little effort at trying to be humble. I don't think that's that difficult.
Anyway, I'll figure it out, don't worry, I was only trying to set up a constructive discussion as the panel says, but apparently I badly misjudged everything.

[zeertzjq]

Sorry, I couldn't decide how to answer the question directly. I think #37075 contains most relevant information.

[justinmk]

It means that during Nvim startup, while Nvim tries to detect your terminal background-color, your terminal took too long to respond.

You can try increasing this to something like 1000:

neovim/runtime/lua/vim/_core/defaults.lua

Line 893 in 5cbb9d6

if not vim.wait(100, function()

[jpalus]

Seeing the message each and every time I open neovim on remote host when using mobile network with high latency I'd go even further and would prefer to have an option to skip this warning altogether. Especially that dismissing this message takes orders of magnitude more time during startup than receiving this DSR response.

I don't get what's the added value in showing such a verbose message to regular users (perfectly fine in some verbose logging or startup tracing/profiling mode) but I wouldn't mind if there was at least an option to disable it.

[justinmk]

see #38699 (but please avoid comments there)

[jpalus]

Pity the PR goes in the direction of choosing between disabling background detection or having warning message, while all I want is not to have warning message. I wouldn't even notice longer startup time over SSH with high latency in the first place (because you're convinced it's just data stuck somewhere) while I certainly notice warning message.

[zeertzjq]

With #38901 the warning message is still present, but you shouldn't have to dismiss it.

[jpalus]

That's a step forward. Thanks. Would it be possible to get rid of it completely though? For example by introducing new section to :checkhealth and shift it there?