some messages are skipped when sent at the same time

[antoinemadec]

issue

When messages are sent at the same time (with events or with async like in mason.nvim), multiple messages sometimes "collide" and overwrite one another to only leave the newest appear.

ui.nvim history is also approximative in that case and does not match vim's :messages anymore.

reproduction

nvim --clean -u init.lua init.lua, where init.lua is:

vim.opt.updatetime     = 100

local function notify(msg, level)
  level = level or vim.log.levels.INFO
  vim.notify(msg, level, {})
end

vim.api.nvim_create_autocmd("CursorHold", {
    pattern = "*",
    callback = function() notify("bar0 was successfully uninstalled.") end,
})
vim.api.nvim_create_autocmd("CursorHold", {
    pattern = "*",
    callback = function() notify("bar1 was successfully uninstalled.") end,
})
vim.api.nvim_create_autocmd("CursorHold", {
    pattern = "*",
    callback = function() notify("bar2 was successfully uninstalled.") end,
})
vim.api.nvim_create_autocmd("CursorHold", {
    pattern = "*",
    callback = function() notify("bar3 was successfully uninstalled.") end,
})

-- ui.nvim
vim.opt.rtp:prepend("$PWD")
require("ui").setup({})

Then use j and k to move around and see the problems described in the issue section.

[OXY2DEV]

I have fixed the issue with the history being different.

When messages are sent at the same time (with events or with async like in mason.nvim), multiple messages sometimes "collide" and overwrite one another to only leave the newest appear.

Isn't that how it's supposed to be? Certain plugins(e.g. nvim-treesitter) use messages like a loading screen because of this behavior.

[antoinemadec]

I don't think that's the intended behavior no.

Sending multiple vim.notify should stack up. This is the default behavior of all the notify plugins I have used before.

[OXY2DEV]

I don't think that's the intended behavior no.

Not every type of message behaves the same way( vim.notify, echo etc. are handled differently).

Sending multiple vim.notify should stack up.

Certain messages are always sent with replace_last = true. So that wouldn't happen for those.

You can check this behavior in your demo even after removing ui.nvim. Messages don't get stacked here.

[OXY2DEV]

See here,

show.mp4

[OXY2DEV]

This is the default behavior of all the notify plugins I have used before

Are you sure the messages weren't made via print()/vim.print()?

[antoinemadec]

My example uses vim.notify and sometimes they overwrite each other.

What i am saying is that sending 4 vim.notify back to back or "at the same time with cursor hold" should behave the exact same way.

Do you agree?

[OXY2DEV]

My example uses vim.notify and sometimes they overwrite each other.

On my machine, this happens with nvim --clean too.

What i am saying is that sending 4 vim.notify back to back or "at the same time with cursor hold" should behave the exact same way.

Unfortunately, as far as I understand that's not how the messages are handled internally in Vim.

This was probably the behavior before 0.11(they did some refactoring to the message UI). You can try downgrading to 0.10 and see if the behavior changes.

[OXY2DEV]

Also the reason it happens sometimes is because when a message is shown first, replace_last is set to true automatically for any new message.

After a while this resets to false again.

[OXY2DEV]

@antoinemadec I have checked with noice.nvim and it appears that replace_last isn't respected by it.

[OXY2DEV]

You can now set this in your config to have each message show up individually,

message = {
    respect_replace_last = false
}