fix: only call denops#plugin#wait after denops#plugin#load#44
Merged
Conversation
Copilot created this pull request from a session on behalf of
Shougo
June 16, 2026 01:46
View session
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
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.
When a lazy plugin with a denops component is triggered (e.g. via
on_event = 'InsertEnter') before denops finishes its async startup,denops#plugin#waitwas executing unconditionally whenever the server wasn't'stopped'— even thoughdenops#plugin#loadhad been skipped (requires'running'). Sinceplugin.sourcedis set totruebefore the denops section, the plugin gets permanently marked as sourced with its denops component never actually loaded.Change
Move
denops#plugin#waitinside thedenops#server#status() ==# 'running'block so it only fires whendenops#plugin#loadwas actually called: