Initialize clipboard asynchronously to avoid startup delay in WSL2#4105
Open
PetarPeychev wants to merge 1 commit into
Open
Initialize clipboard asynchronously to avoid startup delay in WSL2#4105PetarPeychev wants to merge 1 commit into
PetarPeychev wants to merge 1 commit into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
I had a very slow startup time in WSL2. Tracked this down to clipboard initialization in clipper.GetClipboard. Either the inherent WSL2 interop cost or perhaps the "powershell.exe Get-Clipboard" .NET cold start.
Changes
There may be a better way to solve this (neovim seems to use https://github.com/equalsraf/win32yank) but I've just moved the initialization to a goroutine here. This reduced startup on my machine from ~800ms down to ~60ms.