-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: messages printed during start up are missing #799
Comments
I'm pretty sure this doesn't have anything to do with Noice itself, but rather with the order that lazy.nvim loads plugins. If noice is loaded after the messages are printed, then it wouldn't register the messages and add it to its own logs. If you want to see any possible startup errors, then making the plugins with those possible errors have |
It is not good for me to set I think Noice should read the lines from |
* up/main: fix(messages): include any messages before Noice was started as one history_show message. Fixes folke#799 feat(config): added `Noice all` to show ALL messages captured by Noice. See folke#769 chore(main): release 2.0.3 (folke#800) chore(build): auto-generate vimdoc fix(nui): safely destroy any create window/buffers during E565 errors. Fixes command preview fix(hacks): use feedkeys instead of input to force redraw
Did you check docs and existing issues?
Neovim version (nvim -v)
v0.9.5
Operating system/version
MacOS 14.1.2 (23B2091)
Describe the bug
The messages printed by
vim.print
andvim.notify
during start up are missing in Noice message window and Noice history window.For common scenario, some plugins may print warning messages during start up. User will not see these messages and
:Noice history
also miss them.Steps To Reproduce
nvim -u ./repro.lua
:messages
to view the "warning" and "hello" messages.:Noice history
to view the messages in Noice window. And it is empty.Expected Behavior
Show the "warning" and "hello" messages in Noice message window. And
:Noice history
includes these message.Repro
The text was updated successfully, but these errors were encountered: