Add a delay before printing usage message #7
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rafikdraoui
force-pushed
the
usage-delay
branch
from
ec911a4 to
5b45436
Compare
Without this, the message is cleared before the UI is fully initialized.
This also allows us to use the default INFO log level. Previously, using
WARN level was required to make the message display. But now it seems
like even WARN level is not enough to keep the message displayed.
I'm not a fan of using those `time.sleep()`-type of "fixes". And it's
possible that using a 100ms delay is not appropriate for all set ups,
but just happens to work for me as of September 4 2025. But I don't have
time right now to find a proper fix, let alone investigate and bisect
when the behaviour changed in Neovim.
This can be replicated with:
$ nvim --clean --noplugin -c 'lua vim.notify("hello")'
versus
$ nvim --clean --noplugin -c 'lua vim.defer_fn(function() vim.notify("hello") end, 100)'
The first one doesn't have any message in the `:messages` section, while
the latter does (using Neovim v0.11.3).
rafikdraoui
force-pushed
the
usage-delay
branch
from
5b45436 to
6602eb6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Without this, the message is cleared before the UI is fully initialized. This also allows us to use the default INFO log level. Previously, using WARN level was required to make the message display. But now it seems like even WARN level is not enough to keep the message displayed.
I'm not a fan of using those
time.sleep()-type of "fixes". And it's possible that using a 100ms delay is not appropriate for all set ups, but just happens to work for me as of September 4 2025. But I don't have time right now to find a proper fix, let alone investigate and bisect when the behaviour changed in Neovim.This can be replicated with:
versus
The first one doesn't have any message in the
:messagessection, while the latter does (using Neovim v0.11.3).